Communication generation using sparse indicators and sensor data

ABSTRACT

Techniques, systems, and products for analyzing sparse indicators and sensor data and generating communications are disclosed. The sensors may be associated with or incorporated into devices that may automatically relay sensor data for use in analyses and communication generation.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. application Ser. No.15/406,394, filed Jan. 13, 2017, now U.S. Pat. No. 9,774,508, issued onSep. 26, 2017. U.S. application Ser. No. 15/406,394 is acontinuation-in-part of U.S. application Ser. No. 15/169,294, filed May31, 2016, now U.S. Pat. No. 9,584,882, issued Feb. 28, 2017, whichclaims the benefit of and priority to U.S. Provisional Application No.62/261,982, filed Dec. 2, 2015. U.S. application Ser. No. 15/406,394also claims the benefit of and priority to U.S. Provisional ApplicationNo. 62/304,487, filed Mar. 7, 2016. This application is also acontinuation-in-part of U.S. application Ser. No. 15/489,473, filed Apr.17, 2017, now U.S. Pat. No. 9,773,031, issued on Sep. 26, 2017. U.S.application Ser. No. 15/489,473 claims the benefit of and priority toU.S. Provisional Application No. 62/324,080, filed Apr. 18, 2016. Thisapplication is also a continuation-in-part of U.S. application Ser. No.15/163,191, filed May 24, 2016, now U.S. Pat. No. 9,785,792, issued onOct. 10, 2017. U.S. application Ser. No. 15/163,191 claims the benefitof and priority to U.S. Provisional Application No. 62/303,531, filedMar. 4, 2016. This application is also a continuation-in-part of U.S.application Ser. No. 15/133,089, filed Apr. 19, 2016, now. U.S. Pat. No.9,811,552, issued on Nov. 7, 2017. U.S. application Ser. No. 15/133,089claims the benefit of and priority to U.S. Provisional Application No.62/150,218, filed Apr. 20, 2015, and U.S. Provisional Application No.62/274,660, filed Jan. 4, 2016. Each and all of the aforementionedapplications are hereby incorporated by reference in their entiretiesfor all purposes.

FIELD

Methods and systems disclosed herein relate generally to processing ofdata obtained from various sources for use in communication generation.Specifically, a sparse indicator can be analyzed and used in combinationwith sensor data to characterize states or status information, which inturn are used to generate communications.

BACKGROUND

Computational resources have become less expensive, and processingcapabilities have become more sophisticated. In addition, sensors haveproliferated, making sensor data more commonly available. Accordingly,the number and size of data sets has been exponentially increasing. Itis therefore important to decide how to effectively and efficientlyprocess these data sets. One approach is to use reference data sets andto selectively concentrate on how individual data sets differ from oneor more reference data sets. By detecting these differences, a morecompact representation of a data set is reached.

SUMMARY

Described herein are devices, systems, methods, and computer programproducts for facilitating generation of communications based on sparseindicator information and sensor data. In an aspect, systems forgenerating communications based on sparse indicator information andsensor data are provided. In some embodiments, a system comprises one ormore hardware processors and a non-transitory computer readable storagemedium in data communication with the one or more hardware processors,the non-transitory computer readable storage medium comprisinginstructions that, when executed by the one or more hardware processors,cause the one or more hardware processors to perform operationsincluding receiving, at the one or more hardware processors, a firstquery from a first remote device, such as a first query that includes anelectronic request to conduct a status analysis for a client determiningan identifier associated with the client; querying a data store with theidentifier to identify one or more sparse indicators associated with theclient, such as where each sparse indicator corresponds to an instanceof one or more values in the first data set differing from acorresponding one or more values in a reference data set; receiving, inresponse to the query, (such as by retrieving) the one or more sparseindicators associated with the client from the data store; performing afirst status analysis using the one or more sparse indicators, such as afirst status analysis that corresponds to determination of a firstlikelihood of the client transitioning to a particular state; obtainingsensor data associated with the client, such as sensor data providing anindication of a current quality of the client; performing a secondstatus analysis using the one or more sparse indicators and the sensordata associated with the client, such as a second status analysis thatcorresponds to determination of a second likelihood of the clienttransitioning to the particular state; generating a communicationindicative of the second likelihood of the client transitioning to theparticular state; and transmitting the communication to the first remotedevice. Optionally, the instructions may be executed by the one or morehardware processors to perform methods described herein.

In another aspect, computer implemented methods for generatingcommunications based on sparse indicator information and sensor data areprovided. In one example embodiment, a method of this aspect comprisesreceiving, at one or more hardware processors, a first query from afirst remote device, such as a first query that includes an electronicrequest to conduct a status analysis for a client; determining anidentifier associated with the client; querying a data store with theidentifier to identify one or more sparse indicators associated with theclient, such as where each sparse indicator corresponds to an instanceof one or more values in the first data set differing from acorresponding one or more values in a reference data set; receiving, inresponse to the query, the one or more sparse indicators associated withthe client from the data store; performing a first status analysis usingthe one or more sparse indicators, such as a first status analysis thatcorresponds to determination of a first likelihood of the clienttransitioning to a particular state; obtaining sensor data associatedwith the client, such as sensor data providing an indication of acurrent quality of the client; performing a second status analysis usingthe one or more sparse indicators and the sensor data associated withthe client, such as a second status analysis that corresponds todetermination of a second likelihood of the client transitioning to theparticular state; generating a communication indicative of the secondlikelihood of the client transitioning to the particular state; andtransmitting the communication to the first remote device.

Optionally, methods of this aspect may further comprise generating afirst communication indicative of the first likelihood of the clienttransitioning to the particular state; and transmitting the firstcommunication to the first remote device. Optionally, methods of thisaspect may further comprise identifying an aggregated likelihood of aplurality of other clients each transitioning to the particular state.Optionally, the communication includes the aggregated likelihood.

Optionally, methods of this aspect may further comprise generating oneor more targets for the client, such as one or more targets that areassociated with changing the second likelihood of the clienttransitioning to the particular state. Optionally, the communicationincludes the one or more targets. In some embodiments, methods of thisaspect may further comprise receiving additional sensor data related tothe one or more targets or providing an updated indication of an updatedstate of the client; performing a third status analysis using the one ormore sparse indicators, the sensor data, and the additional sensor, suchas a third status analysis that corresponds to determination of a thirdlikelihood of the client transitioning to the particular state;generating a communication indicative of the third likelihood of theclient transitioning to the particular state; and transmitting thesecond communication.

Optionally, methods of this aspect may further comprise transmitting arequest for permission to access the one or more sparse indicatorsassociated with the client; and receiving a response includingauthorization to access the one or more sparse indicators associatedwith the client. Optionally, querying the data store includes using theauthorization, such as by transmitting an authorization code or keycorresponding to the authorization.

In various embodiments, the sensor data includes one or more of chemicalsensor data, potentiometric sensor data, solute sensor data,microfluidic sensor data, environmental sensor data, activity sensordata, accelerometer data, altitude sensor data, biometric sensor data,location sensor data, weather sensor data, biometric sensor data,biomarker sensor data, pH sensor data, cytometric sensor data, opticalsensor data, smoke detector data, particulate sensor data, electricalcurrent sensor data, electrical resistance sensor data, and electricalimpedance sensor data. For example, in embodiments, the sensor datacorresponds to sensor data obtained by one or more sensors associatedwith the client, such as attached to or worn by a client or located at asame location as the client. It will be appreciated that, in someembodiments, the sensor may be used to identify a biomarker of a client.It will be appreciated that, in some embodiments, sensor datacorresponds to raw data signals obtained from one or more sensors.Optionally, sensor data may correspond to processed data derived fromraw data signals obtained from one or more sensors.

In some embodiments, obtaining the sensor data includes transmitting asecond query to a second remote device, such as a second query thatincludes a request for the sensor data associated with the client; andreceiving, in response to the second query, the sensor data associatedwith the client. For example, the second remote device may be a clouddevice or a server device. Optionally, the query may be associated witha permission or authorization code or key that provides access to thesensor data.

In another aspect, non-transitory computer readable storage mediums forgenerating communications based on sparse indicator information andsensor data are provided. In embodiments, the non-transitory computerreadable storage medium comprises instructions that, when executed byone or more processors, cause the one or more processors to performoperations, such as aspects or steps of one or more methods disclosedherein. Optionally, the operations include receiving, at the one or morehardware processors, a first query from a first remote device, such as afirst query that includes an electronic request to conduct a statusanalysis for a client; determining an identifier associated with theclient; querying a data store with the identifier to identify one ormore sparse indicators associated with the client, such as where eachsparse indicator corresponds to an instance of one or more values in thefirst data set differing from a corresponding one or more values in areference data set; receiving, in response to the query, the one or moresparse indicators associated with the client from the data store;performing a first status analysis using the one or more sparseindicators, such as a first status analysis that corresponds todetermination of a first likelihood of the client transitioning to aparticular state; obtaining sensor data associated with the client, suchas sensor data providing an indication of a current quality of theclient; performing a second status analysis using the one or more sparseindicators and the sensor data associated with the client, such as asecond status analysis that corresponds to determination of a secondlikelihood of the client transitioning to the particular state;generating a communication indicative of the second likelihood of theclient transitioning to the particular state; and transmitting thecommunication to the first remote device.

Some embodiments described herein relate to a process for processingrequests to conduct disease-risk analyses, conducting using geneticinformation to generate risk variables for developing one or morediseases and/or for controlling access to genetic data.

In some embodiments, genetic data is analyzed in combination with datafrom one or more other sources. The other data could include datacollected from a movement detector (e.g., phone accelerometer, Fitbit,or smart watch), data from a protected health information record (e.g.,from a physician's office and/or including a test result), or cameradata. A central or remote server may facilitate interactions between auser device and other device to authorize use of the other data. Theintegrated analysis of the various data types may result in generationof more accurate risk variables that represent a risk of developing aparticular disease.

In some embodiments, a system may be configured to prioritize ensuringthat clients are provided with evidence-based information prior toauthorizing biological analyses and/or to enable clients to authorizepost-hoc biological analyses. Accordingly, a graphical user interfacemay be generated and transmitted to a client device that identifiesspecific genetic data (e.g., genes) to be used in an analysis and mayidentify evidence supporting the purported pertinence. The interface mayfurther be configured to accept a user input that authorizes access toand analysis of the specific genetic data. Because it is recognized thatadditional data may later as being additionally pertinent and/oridentify some or all of the original data points as being pertinent tothe risk in a different way, the interface may also be configured toaccept (a same or different) input permitting post-hoc analysis (whichmay involve a new laboratory analysis of a stored sample).

In some embodiments, genetic data of clients are analyzed in a temporalmanner that roughly corresponds to a time that the samples werereceived. Reports identifying risk variables generated based on thedata, similarly, may be sent to client devices in this rough order. Uponidentifying a new type of genetic data that pertains to the condition,all (or a set) of the samples can then be assessed in a near-batch mode.This updated analysis may involve new laboratory analysis of storedsamples or a retrieval of data previously collected but not necessarilyused. Updated reports may then be sent to client devices in aconditional or unconditional manner. For example, updated reports may betransmitted to a device of each client for which an updated analysis wasperformed or to a device of each client for which an updated analysisyielded a particular type of result (e.g., a changed result). Post-hocanalysis may pertain to a same condition, a different condition or atreatment efficacy.

In some embodiments, a data store may store, for each of one or moresubjects, part or all of a subject's genome. An app developer mayrequest access to part or all of the data, but access constraints may beestablished to ensure that a subject has authorized such access andpotentially that such authorization is reasonable. For example, it maybe required that a developer have presented indications as to which datais being requested and/or why to a user and that a user have providedinput authorizing the request. As another example, it may be requiredthat all of a developer's requested data be informative (e.g., assupported based on industry knowledge or developer data) of a conditionbeing genetically assessed.

In some embodiments, an app developer may request access to part or allof the data. Such data access may present privacy concerns above andbeyond normal data, as it can relate to a subject's health and may besubject to HIPAA. Access restrictions can therefore be accordinglyestablished. The restrictions may be established in a manner that allowsdifferential types of access to data to be granted based on a permissiontype granted by a subject. For example, a first permission type maygrant access to genetic data along with other data (e.g., including asubject's name, past diagnoses, activity patterns, etc.), while a secondtype may permit access to the genetic data but restrict or deny accessto the other data.

In some embodiments, interfaces may be provided to allow developers tospecify particular genetic and/or epigenetic data of interest. Aninterface may identify (for example) what types of data (e.g., what genesequences) may be available (e.g., for at least one client) or that areavailable for a given client. Thus, for example, one or more inputs maybe collected to identify a client and one or more genes of interest.Further, a developer may be able to specify, via an interface, a type ofrequested data (e.g., a sequence, variance detection and/orcategorization). The request can then be processed to ensure that thedata is available and that the developer is authorized to access thedata. The authorization check may include sending an email to a clientrequesting an indication as to whether authorization is being provided.

The terms and expressions which have been employed are used as terms ofdescription and not of limitation, and there is no intention in the useof such terms and expressions of excluding any equivalents of thefeatures shown and described or portions thereof, but it is recognizedthat various modifications are possible within the scope of theinvention claimed. Thus, it should be understood that although thepresent invention has been specifically disclosed by embodiments andoptional features, modification and variation of the concepts hereindisclosed may be resorted to by those skilled in the art, and that suchmodifications and variations are considered to be within the scope ofthis invention as defined by the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

Illustrative embodiments of the present invention are described indetail below with reference to the following drawing figures:

FIG. 1 shows a representation of a data processing network, inaccordance with some embodiments.

FIG. 2 shows a communication exchange between systems and devices of adata processing network, in accordance with some embodiments.

FIG. 3 shows a representation of an example communication network, inaccordance with some embodiments.

FIG. 4 shows a process flow, in accordance with some embodiments.

FIG. 5 shows an illustration of a work flow iteration, in accordancewith some embodiments.

FIG. 6 shows a block diagram of an example data processing networkdevice or system, in accordance with some embodiments.

FIG. 7 illustrates components of a data processing network device orsystem, in accordance with some embodiments.

FIG. 8 shows a representation of a system for generating communications,in accordance with some embodiments.

FIG. 9 shows a representation of a system for generating communicationsusing sparse indicator information and sensor data.

FIG. 10 shows a representation of a process for generatingcommunications using sparse indicator information and sensor data.

FIG. 11 shows a representation of a system for generating communicationsincluding target information using sparse indicator information andsensor data.

FIG. 12 shows a communication exchange between systems and devices of adata processing network, in accordance with some embodiments.

FIG. 13 shows a representation of a process for generatingcommunications including target information using sparse indicatorinformation and sensor data.

FIG. 14 shows a representation of a genetic assessment network, inaccordance with some embodiments.

FIG. 15 shows an embodiment of a process for conducting risk analysesbased on genetic information.

FIG. 16 shows an embodiment of a process for conducting risk analysesbased on genetic information.

FIG. 17 shows an embodiment of a process for conducting risk analysesbased on genetic information.

FIG. 18 shows an embodiment of a process for evaluating genetic-dataqueries based relevance assessments.

FIG. 19 shows an embodiment of a process for differentially respondingto requests for access to genetic data based on subject-providedpermission types.

FIG. 20 shows an embodiment of a process for processing custom queriesfrom external assessment devices for genetic and/or epigenetic data.

DETAILED DESCRIPTION

The ensuing description provides preferred exemplary embodiments only,and is not intended to limit the scope, applicability or configurationof the disclosure. Rather, the ensuing description of the preferredexemplary embodiments will provide those skilled in the art with anenabling description for implementing various embodiments. It isunderstood that various changes may be made in the function andarrangement of elements without departing from the spirit and scope asset forth in the appended claims.

Specific details are given in the following description to provide athorough understanding of the embodiments. However, it will beunderstood that the embodiments may be practiced without these specificdetails. For example, circuits, systems, networks, processes, and othercomponents may be shown as components in block diagram form in order notto obscure the embodiments in unnecessary detail. In other instances,well-known circuits, processes, algorithms, structures, and techniquesmay be shown without unnecessary detail in order to avoid obscuring theembodiments.

Also, it is noted that individual embodiments may be described as aprocess which is depicted as a flowchart, a flow diagram, a data flowdiagram, a structure diagram, or a block diagram. Although a flowchartor diagram may describe the operations as a sequential process, many ofthe operations may be performed in parallel or concurrently. Inaddition, the order of the operations may be re-arranged. A process isterminated when its operations are completed, but could have additionalsteps not included in a figure. A process may correspond to a method, afunction, a procedure, a subroutine, a subprogram, etc. When a processcorresponds to a function, its termination may correspond to a return ofthe function to the calling function or the main function.

In general the terms and phrases used herein have their art-recognizedmeaning, which can be found by reference to standard texts, journalreferences and contexts known to those skilled in the art. The followingdefinitions are provided to clarify their specific use in the context ofthe invention.

The term “machine-readable storage medium” or “computer-readable storagemedium” includes, but is not limited to, portable or non-portablestorage devices, optical storage devices, and various other mediumscapable of storing, containing, or carrying instruction(s) and/or data.A machine-readable storage medium or computer-readable storage mediummay include a non-transitory medium in which data may be stored and thatdoes not include carrier waves and/or transitory electronic signalspropagating wirelessly or over wired connections. Examples of anon-transitory medium may include, but are not limited to, a magneticdisk or tape, optical storage media such as compact disk (CD) or digitalversatile disk (DVD), flash memory, memory or memory devices. Acomputer-program product may include code and/or machine-executableinstructions that may represent a procedure, a function, a subprogram, aprogram, a routine, a subroutine, a module, a software package, a class,or any combination of instructions, data structures, or programstatements. A code segment may be coupled to another code segment or ahardware circuit by passing and/or receiving information, data,arguments, parameters, or memory contents. Information, arguments,parameters, data, etc. may be passed, forwarded, or transmitted via anysuitable means including memory sharing, message passing, data storewrites/reads, network transmission, etc.

Furthermore, embodiments may be implemented by hardware, software,firmware, middleware, microcode, hardware description languages, or anycombination thereof. When implemented in software, firmware, middlewareor microcode, the program code or code segments to perform the necessarytasks (e.g., a computer-program product) may be stored in amachine-readable medium. A processor(s) may perform the necessary tasks.

Systems depicted in some of the figures may be provided in variousconfigurations. In some embodiments, the systems may be configured as adistributed system where one or more components of the system aredistributed across one or more networks in a cloud computing system.

FIG. 1 shows a representation of an assessment network 100. In addition,FIG. 2 illustrates interactions between various systems or components ofassessment network 100 to illustrate the flows of data and materials,for example. Assessment system 105 may, for example, receive anelectronic request 205 from a requestor device 110. Assessment system105 may include one or more electronic devices (e.g., storage devices,servers, and/or computers) and may, but not need, reside partly orentirely at a remote server. Requestor device 110 may be configured andlocated to receive input from a requestor 115. In one instance,requestor device 110 a is located in an external facility 120. In oneinstance, requestor device 110 b includes an internally linked requestordevice 110 b, such as one that itself receives invitations, such as fromassessment system 105, to generate electronic requests.

Request 205 may include instructions to conduct a data-set analysis, forexample. Optionally, request 205 may be encrypted prior to transmission;such an electronic request may be decrypted upon receipt. Request 205may identify, or otherwise indicate, one or more states to be evaluatedduring the analysis and/or during an assessment. Request 205 mayidentify a client and/or include additional data pertaining to theclient, such as client-identifying data.

The client may be equated to, by assessment system 105, a client device130. In some instances, a client device 130, associated with client 125,initially transmits a preliminary electronic request for the analysisand/or assessment to assessment system 105. For example, such apreliminary electronic request may be initiated via interaction with awebsite associated with assessment system 105. The same or a subsequentpreliminary request may identify a particular requestor (e.g., by name,office location, phone number, and/or email address) and/or may requestthat a requestor 115 b associated with an internally linked requestordevice 110 b submit such a request.

When a particular entity is identified in a preliminary electronicrequest, assessment system 105 may identify a destination address (e.g.,IP address or email address) associated with the entity and transmit acommunication identifying information associated with the preliminaryrequest (e.g., the client, a type of analysis, and so on). Thecommunication may include a partial instruction and/or an input fieldthat would confirm that the request of the client 125 is to be generatedand transmitted back to assessment system 105. Such a communication mayfacilitate receipt of the electronic request 205 from requestor device110 b.

When it is requested that a requestor 115 b associated with aninternally linked requestor device 110 b submit such a request,assessment system 105 may transmit a similar communication to arequestor device 110 b that may have been selected from among multipleinternally linked requestor devices. The selection may be based on aload balancing technique, availability hours, expertise, locations ofthe multiple requestor devices, a pseudo-random selection technique,and/or an entity affiliation.

Once request 205 has been received from a requestor device 110 (e.g., inresponse to a preliminary request from a client device 130), assessmentsystem 105 may evaluate, such as at block 220, the request 205 to ensurethat all required data has been provided and that all required datapertaining to client 125 has been identified (e.g., via the request, apreliminary request and/or stored data). If assessment system 105determines that all required information has not been identified, arequest 210 for such information may be transmitted to requestor device110 and/or client device 130. The request 205 may be updated with thisinformation and an updated electronic request 215 may be transmitted toassessment system 105. In various instances, an object provided to auser depends on an analysis requested, whether, and what kind of, newdata-generation processing of a material is required for the analysis, anumber of data-set units being assessed (e.g., and whether they havebeen previously assessed), a number and/or type of analyses beingrequested, a number and/or type of analyses previously requested, anumber and/or type of analyses predicted to be requested subsequently, astate for which a progression prediction is being requested, whether auser is granting other entities' access to the client's data or results,whether a user is authorizing additional analyses to be performed on theclient's data, and/or whether a user is granting permission to sendoffers to request user access to results or reports other than thoseinitially being requested.

When all required information has been provided, assessment system 105may send an instruction communication 225 to a distribution device 135.Optionally, communication 225 may be encrypted prior to transmission;such an encrypted communication may be decrypted upon receipt.Optionally, communication 225 may be transmitted using communicationssystem 108 and/or over one or more network links, such as includingtransmission, at least in part, over a public communications network,such as the Internet. Communication 225 may include, for example, a nameand address of client 125 and, in some instances, an indication as towhat is to be provided to client 125 for collection of a material forsubsequent analysis. For example, a request 205 may indicate a type ofanalysis that is to be performed on a material (e.g., an analysispertaining to a likelihood of getting one or more particular types ofstates) and/or a type of material (e.g., type of sample) that is to beanalyzed. Communication 225 may identify the type of analysis, type ofmaterial, and/or kit associated with collection of the material. Thecommunication 225 may thus facilitate and/or trigger a physicaldistribution of instructions 230, which may include a kit or othersample collection materials, to a client address. The instructions 230may include, for example, instructions as to how to collect a material,a container for storing the material and/or information pertaining to aninstruction or type of analysis to be conducted. Alternatively, theinstructions 230 may be provided to a facility 120, such as may beassociated with a requestor 115 a, who may aid client 125 in obtainingthe material.

A material 235 from client 125 may then be directed to and received at adata generator 140 for analysis 240. Data generator 140 may be, forexample, part of a facility. Data generator 140 may include one or moreassessment devices 145 configured to generate data reads, data elements,or data sets for various data-set units using the material 235 as partof analysis 240. For example, an assessment device 145 may include adata-characterizer device (e.g., sequencer and/or polymerase chainreaction machine). Data generator 140 may further include one or moredevices 150, such as a desktop or laptop computer. Generated data 245generated by or at one or more devices (e.g., assessment device 145 ortechnician device 150) may be stored at a data store 155, which may beremote from all data generator devices or part of a data generatordevice. The data 245 may, for example, include identifying clientinformation (e.g., a name and address), facility information (e.g.,location and name), device specifications (e.g., manufacturer and modelof assessment device) and data. In some embodiments, a facility, such asfacility 120 or data generator 140, may correspond to a lab.

In some instances, data is optionally collected or requested from one ormore external systems 249. Thus, assessment system 105 may transmit oneor more other data requests 250 and one or more other data transmissions255 may provide the other data. For example, one or more data setsand/or one or more processed versions thereof (e.g., identifying one ormore sparse indicators) corresponding to an existing or new client maybe received from an external system 249, As another example, assessmentsystem 105 may transmit a client data set to an external system 249, andexternal system 249 may then return a result of an assessment of theclient data set. As yet another example, other data may include a dataset (or results based on such data) corresponding to another individual(e.g., an entity related to a client and/or an entity sharing acharacteristic with a client). The other individual may be, for example,identified based on input from the client and/or automaticallyidentified (e.g., based on a query of a data store to identify clientsassociated with inputs or results indicating a shared characteristic orrelationship). In some instances, a state assessment variable may begenerated based on data from multiple other people, and the data foreach other person may be weighted based on (for example) how closelyrelated the person is with a client and/or how many or whichcharacteristics the person shares with a client.

An access control device 160 a may control which devices and/or entitiesmay gain access to the data 245, which may apply to devices and/orentities internal to data generator 140 and/or to devices and/orentities external to data generator 140. Access control device 160 a mayimplement one or more rules, such as restricting access to client datato one or more particular devices (e.g., associated with assessmentsystem 105). Such access may further or alternatively be controlled vialogins, passwords, device identifier verification, etc.

In various instances, access control device 160 a controls access viacontrol of pushed transmissions and/or via control of processing pullrequests. For example, a rule may indicate that data 245 pertaining to amaterial, such as a sample, is to automatically be transmitted to aparticular assessment system 105 (and/or device associated therewith)upon completion of a facility-based assessment or detection ofparticular data (e.g., data matching a request). Access control device160 a may then monitor for such a criterion to be met and may thengenerate and transmit appropriate data.

Data 245 may include a plurality of data reads, data elements, or sets(e.g., each data read in the plurality of data reads corresponding to asame client, or at least some of the plurality of data readscorresponding to different clients). In various instances, data 245 maybe transmitted to assessment system 105 in a batch-mode, in a streamingmode, in real-time as data is produced, and/or upon request. Data 245may also be stored at a data store local or remote to data generator140. A given transmission or stream may include data that corresponds toa single, or in other instances to multiple, client, sample, and/or datareads. In some instances, access control device 160 a evaluates one ormore transmission conditions, which may indicate, for example, whetherand/or what data is to be transmitted given a quantity of data collected(e.g., generally, since a past transmission and/or for a given client orsample) and/or given a time since a previous transmission. In oneinstance, as data reads are generated by an assessment device, a dataset is generated so as to include each new data read and one or moreidentifiers (e.g., of a client, sample, time and/or facility device).The data may then be transmitted via a discrete communication (e.g., viaFTP, over a webpage upload, email message, or SMS message) to assessmentsystem 105. In one instance, the data may then be appended to a streamthat is being fed to assessment system 105.

It will be appreciated that assessment network 100 may, in someinstances, include multiple data generators 140, each of which mayinclude an assessment device 145, technician device and/or accesscontrol device 160 a. Further, a given data generator 140 may, in someinstances, include multiple assessment devices 145, multiple techniciandevices 150 and/or multiple access control devices 160 a. Thus, data 245received at assessment system 105 may include data collected by and/orderived from data collected by different assessment devices, which mayresult in the data having different biases, units, and/orrepresentation. Similarly, personnel operating different techniciandevices 150 may utilize different protocols and/or data interpretationtechniques, which may again result in receipt of data at assessmentsystem 105 that has different biases, units, variables, and so on.Further, even data originating from a same device may, in time, exhibitdifferent biases, units, and so on, which may be a result of amanipulation of a control of the device and/or equipment wear.

Thus, in some instances, assessment system 105 performs a comparisonacross data 245 received from a data generator device (e.g., an accesscontrol device 160 a or directly from an assessment device 145 ortechnician device 150) associated with data generator 140. Thecomparison may be across, for example, data collected at differentfacilities, data based on measurements collected at different devices,and/or data collected at different times. It will be appreciated thatthe comparison may include a direct comparison of collected data orcomparing preprocessed versions of the collected data. For example,received data may first be preprocessed via a transformation and/ordimensionality-reduction technique, such as principal componentanalysis, independent component analysis, or canonical correspondenceanalysis.

The comparison may include, for example, performing a clusteringtechnique so as to detect whether data corresponding to a givenfacility, device, or time period predominately resides in a differentcluster than data corresponding to one or more other facilities,devices, or time periods. The clustering technique may include, forexample, a connectivity based clustering technique, a centroid-basedclustering technique (e.g., such as one using k-means clustering), adistribution-based clustering technique, or a density-based clusteringtechnique.

The comparison may additionally or alternatively include a statisticaltechnique, such as one that employs a statistical test to determinewhether two or more data sets (e.g., corresponding to differentfacilities, devices, or time periods) are statistically different. Forexample, a Chi-square, t-test or ANOVA may be used.

The comparison may additionally or alternatively include a time-seriesanalysis. For example, a regression technique may be used to determinewhether output from a given device is gradually changing in time.

When it is determined that particular data corresponding to a givenfacility, device, or time period is different than data corresponding toone or more other facilities, devices, or time periods (e.g., isassigned to a different cluster than other data or is associated with ap-value below a threshold), a normalization and/or conversion factor mayfurther be identified. For example, a normalization and/or conversionfactor may be identified based on centroids of data clusters and/orinter-cluster distances. As another example, a linear or non-linearfunction may be derived to relate data from a given facility, device, ortime period to other data.

In some instances, a determination that particular data corresponding toa given facility, device, or time period is different than datacorresponding to one or more other facilities, devices, or time periodsmay indicate that data from the given facility, device, or time periodis not to be used. In such instances, an instruction communication maybe sent to a facility to reprocess a material, such as a sample.

In addition to receiving data 245, assessment system 105 may furthercollect one or more other data that may be used to assess, for example,a likelihood for transitioning into a particular state. For example, onetype of other data may include inputs provided at a client device 130,such as inputs that indicate past-state data and/or current-state data,familial-state data and statuses, age, occupation, activity patterns,association with environments having particular characteristics, and soon. The other data may be received by way of one or more other datatransmissions 255 from external system 249. Optionally, other datatransmission 255 may be encrypted prior to transmission; such anencrypted transmission may be decrypted upon receipt. Optionally, otherdata transmission 255 may be transmitted over one or more network links,such as including transmission, at least in part, over a publiccommunications network, such as the Internet. Optionally, other datatransmission 255 may be transmitted over at least a portion ofcommunications system 108.

Another type of other data may include data automatically detected at aclient device 130 or a location associated with the client. For example,a wearable client device may track activity patterns so as to estimatecalories burned per day, or the wearable client device may estimate apulse distribution, client temperature, sleep patterns and/orindoor/outdoor time. This data obtained directly by client device 130may be directly transmitted (e.g., after request 250 and/orauthorization handshake) to assessment system 105 and/or via anotherclient device (e.g., via accessing health-data on a phone or computerdevice). Optionally, other data obtained directly by client device 130may be transmitted over one or more network links, such as includingtransmission, at least in part, over a public communications network,such as the Internet. Optionally, other data obtained directly by clientdevice 130 may be transmitted over at least a portion of a communicationsystem. Optionally, other data obtained directly by client device 130may be part of other data transmission 255.

Optionally, other data may correspond to data obtained by one or moresensors associated with a client or with a location associated with theclient. For example, useful sensor data includes, but is not limited to,chemical sensor data, potentiometric sensor data, solute sensor data,microfluidic sensor data, environmental sensor data, activity sensordata, accelerometer data, altitude sensor data, biometric sensor data,location sensor data, weather sensor data, biometric sensor data,biomarker sensor data, pH sensor data, cytometric sensor data, opticalsensor data, smoke detector data, particulate sensor data, electricalcurrent sensor data, electrical resistance sensor data, and electricalimpedance sensor data. The use of sensor data may be beneficial andadvantageous as the sensors can directly monitor behaviors, actions,states, qualities, client characteristics, environmentalcharacteristics, etc., without necessarily requiring inputs or actionsto be taken by the client to obtain the sensor data. In this way, otherdata can be obtained with limited client interaction.

Yet another type of other data may include record data, which may bestored, for example, at a record data store 165 at and/or associatedwith an external facility, such as one having provided an electronicrequest to perform an analysis or assessment pertaining to a clientand/or one as identified via input at a client device 130. Toillustrate, the other data may identify one or more client reportedexperiences and/or evaluation results for a client or may include aresult of one or more tests.

In some instances, other data may include data pertaining to a differentclient. For example, it may be determined or estimated that a givenclient is related to another client. Such determination or estimationmay be based on inputs detected at a client device identifying one ormore family members (e.g., by name), and a data store may be queried todetermine whether any clients match any of the family memberidentifications. Such relationship determination or estimation mayalternatively or additionally be based on a data set analysis, such thata raw or processed data set from the given client is compared to a rawor processed data set from some or all other clients to identify, forexample, whether any other clients share a threshold portion of a dataset with the client. Upon detecting an above-threshold match, apercentage of value matching may be used to estimate a type ofrelationship between the clients. Upon identifying a related client,other data corresponding to the related client may be identified. Forexample, the other data may include a past or current state or qualityof the related client. The other data may be identified (for example)based on an input provided by the client or the related client or recorddata associated with the related client.

Thus, assessment system 105 may have access to, for a given client, oneor more data sets, data set availability modification data,client-reported data, record data, test data, activity data, and/orother types of data. These data may be detected, assessed, or otherwiseevaluated, at block 260, such as in one or more assessment processes.Data sets may be evaluated to detect and assess sparse indicators, forexample, as described below in further detail. The detection and/orassessment at block 260 may be performed, for example, partly or fullyat assessment system 105. In some instances, the detection and/orassessment at block 260 is performed in a partly or fully automatedmanner. In some instances, the detection and/or assessment at block 260involves processing of inputs provided by a reviewer or evaluator.

Generation of a report, at block 290, may be performed using the resultsof data assessment of block 260. A report transmission 295 may includethe report and be transmitted to client 125 or facility 120, such as byway of client device 130 or requestor device 110 a.

Referring next to FIG. 3, an assessment network 300 is shown in oneembodiment. Assessment network 300 may, but need not, correspond toassessment network 100 shown in FIG. 1. Through the interaction ofmultiple devices and entities, an assessment system 305 may receive datasets corresponding to individual clients. As illustrated, assessmentsystem 305 may connect, via communication system 308, to each of one ormore other systems or devices. Assessment network 300 may also includeadditional systems or devices, as illustrated in FIG. 3. For example,assessment network 300 may include requestor device 310, facility 320,client device 330, data generator 340, and data store 372, in additionto other systems or devices not explicitly depicted in FIG. 3.

Data may be exchanged between various systems or devices of assessmentnetwork, such as by way of communication system 308. Communicationsystem 308 may, for example, include one or more data communicationsystems or networks, such as a wired or wireless data connection thatmakes use of or is compliant with one or more Institute of Electricaland Electronics Engineers (IEEE) networking standards, such as 802.3(Ethernet), 802.11 (Wi-Fi), or 802.16 (WiMAX), or other datacommunications standards such as IEEE 1394 (FireWire), Bluetooth,Universal Serial Bus (USB), Serial ATA (SATA), Parallel ATA (PATA),Thunderbolt, Fibre Channel, Small Computer System Interface (SCSI), GSM,LTE, etc. Communication system 308 may include one or more TCP/IPcompliant interconnections, such as may be present on a private orpublic communications network, such as the Internet. Communicationsystem 308 may further include servers, systems, and storage devices inthe cloud. Communication system 308 may represent or include one or moreintermediate systems or data connections between various othercomponents of assessment network 300. Additionally, communication system308 may represent a direct connection between various other componentsof assessment network 300, such as a direct connection betweenassessment system 305 and data store 372, which may optionally allow forcommunication with data store 372 by other components of assessmentnetwork 300 only by way of assessment system 305, for example. It willbe appreciated that data store 372 may include one or more data stores,which may optionally be linked or otherwise configured or organized toallow for efficient retrieval and storage of data by reference todifferent entries in particular data stores or data tables. For example,data store 372 may comprise a relational database or data store, in someembodiments.

One or more of the devices or systems of assessment network 300 may bepresent at a single location or each may be present at various differentlocations and be in data communication with one another viacommunication system 308, depending on the specific configuration. Forexample, facility 320 and data generator 340 may be at a same location.Requestor device 310 may further be present at facility 320, such as ifpossessed by a requestor personnel, for example. Similarly, clientdevice 330 may also be present at data generator 340 or facility 320,such as if possessed by a client, for example. In some embodiments, oneor more devices or systems of assessment network 300 may be mobiledevices, such as a smartphone, tablet computer, laptop, or other compactdevice, which may facilitate transport between locations or with a useror client. Use of mobile devices may, for example, be advantageous forallowing input to be entered in real-time and/or on request from anylocation in order to facilitate expedient processing and/or analysis ofdata or generation of state assessments.

In one instance, assessment system 305 receives a request communication(e.g., via communication system) from a requestor device 310 thatidentifies a client. Client identifying authentication and/or otherinformation can be received from a client device (e.g., which, in someinstances, is also requestor device 310). Assessment system 305 may thenprime data generator 340 to detect a material associated with the clientand generate a set of reads based thereupon.

Assessment system 305 may process the reads by, for example, aligningindividual reads to a reference data set (e.g., reference genome) andgenerating one or more client data sets. For example, a first clientdata set may include an identifier data set (e.g., a sequence) thatidentifies a base at each of a set of positions, such at each positionalong one or more data-set units (e.g., genes). The identifier data setmay be generated by, for example, identifying a set of identifiers asthose present in the reads aligned to a given position, at the position,and detecting a most common identifier from amongst the set ofidentifiers. A second client data set may include a coverage data setthat identifies, for each position of a set of positions (e.g., at eachposition along one or more data-set units) a number of reads aligned tooverlap with the position. Assessment system 305 may detect one or moredifferences (e.g., variants) using the data set(s). For example, adifference may be identified by detecting a difference, at a givenposition, between a value of the identifier data set and a correspondingvalue of the reference data set. As another example, a difference may beidentified by detecting an abrupt change in a coverage data set (e.g.,such that values abruptly change approximately 2- or 3-fold). A sparseindicator may be defined for each difference so as to identify a type ofdifference observed (e.g., what identifier was present in an identifierdata set as opposed to a reference data set or how a coverage data setchanged) and a position (e.g., with respect to the reference data setand/or along one or more data-set units) at which the difference wasobserved.

Each sparse indicator may be assigned to a bucket, which may reflect apredicted impact of the detected difference. In some instances, a set ofbuckets are defined. Each of one, more or all of the buckets maycorrespond to a predicted likelihood that a client will progress to agiven state. A state may include, for example, utilizing a full memorybank, a condition (e.g., cancer), a quality (e.g., a feature,characteristic, or condition), reduced bandwidth, and/or a connectiondrop. Thus, buckets may reflect whether and/or a degree to which adifference causes the state (e.g., reflecting memory requirements,whether the difference is (e.g., and/or is likely to be) pathogenic orbenign), consumes bandwidth, and/or impairs a connection's stability.For each client, a determination as to how many sparse indicators wereassigned to one or more particular buckets may be used to generate aresult that identifies a state-progression prediction. The result may betransmitted to requestor device 310 and/or client device 330.

Reads, data sets, sparse indicators, bucket assignments and/or resultsmay be stored (e.g., in association with corresponding clientidentifiers) in one or more data stores. In some instances, data may besubsequently retrieved for performing an updated assessment (e.g., usinga new bucketing protocol or result-generation technique), performing adifferent type of assessment and/or transmitting data to another device.

Turning next to FIG. 4, a process flow embodiment 400 is shown.Initially, a test material 405 is obtained from a client. As describedabove, the material 405 may be obtained directly by the client using acollection kit. A client may be able to obtain the material themselves,particularly if the material is easy to collect. Alternatively oradditionally, material 405 is obtained at a facility. Obtaining material405 at a facility may be useful if the material is more difficult toobtain, or if chain-of-custody is a concern.

Material 405 is assessed by a data-characterizer device 410, which maygenerate a plurality of data sets, including coverage data sets andidentifier data sets. As the data sets are determined, they may bestored in data store 415 for subsequent analysis.

Data-characterizer device 410 and data store 415 may be located at asame location, such as a facility. Alternatively, data-characterizerdevice 410 and data store 415 may be remote from one another. In such aconfiguration, transmission of data sets from data-characterizer device410 to data store 415 may occur using any of a variety of datacommunication standards and/or protocols. In one example, data sets aretransmitted from data-characterizer device 410 over a wired and/orwireless network to reach data store 415. In another example, data setsare stored by data-characterizer device 410 directly to a storagemedium, such as a flash drive or hard drive, which may be used tofacilitate relaying data sets to remote data store 415. Optionally, datastore 415 may comprise the storage medium. Data sets stored in datastore 415 may be analyzed by data set analyzer 420. Data set analyzer420 may be located at a same or different location fromdata-characterizer device 410 and/or data store 415.

Depending on the particular configuration, data sets generated bydata-characterizer device 410 and/or stored in data store 415 may beanalyzed individually, in real-time as the data sets are produced, or inbatches, such as upon completion of a plurality of data sets. Data setanalyzer 420 may utilize reference data stored in reference data store425 in analysis of the data sets generated by data-characterizer device410 and/or stored in data store 415.

A variety of analyses may be performed on the data sets by data setanalyzers 420. For example, data set analyzer 420 may align each read ina data set to a portion of one or more reference sets. Data set analyzer420 may also generate coverage data and/or identifier data using readsfrom the data set. Upon completion of the analysis, the informationcorresponding to the data sets (e.g., coverage data and/or identifierdata) and/or alignment indications may be transmitted to and/or storedin one or more results data stores 430, which may correspond to aportion of data store 372.

It will be appreciated that data set analysis may be resource intensive,and thus a plurality of data set analyzers 420 may be used during theanalysis process to distribute the resource burden, for example, and/orincrease the rate at which data sets may be analyzed. For example, if aplurality of alignments are to be evaluated, such as by determining apotential alignment of an individual data set against multiple referencedata sets, it may be desirable to distribute the tasks among multipledata set analyzers 420. Load balancing between a plurality of data setanalyzers 420 may be performed to further enhance the use of resources,for example. Additionally, it may be desirable to compare the data setsstored in data store 415 against multiple reference data sets, such asfrom related family members or from people sharing one or morecharacteristics, as described above, and comparisons of the data setswith different reference data sets may be performed by different dataset analyzers.

Additionally or alternatively, data sets may be analyzed by one or moredata set analyzers 420 to identify one or more sparse indicators.Additionally or alternatively, data sets may be analyzed by one or moredata set analyzers 420 to categorize each data set, alignment, ordetected sparse indicator. Additionally or alternatively, data sets maybe analyzed by one or more data set analyzers 420 to score each dataset, alignment, or detected sparse indicator. Again, sparse indicators,categories, and scores may be transmitted to and/or stored in resultsdata store 430, which may be included in data store 372.

Detecting sparse indicators may include aligning each data set with areference data set. The reference data set may include part of a fullreference data set and/or may include a data set identified based onidentifying median or mode data elements across a plurality of data setderived from samples from a population. In some instances, an alignmentis determined to be accurate throughout the data set, and differencesbetween the data set and reference data set can be represented as sparseindicators, each corresponding to one or more positions (e.g., relativeto an axis of the reference data set or to an axis of the data set). Insome instances, a sparse indicator may further be defined using a valueor identifier data of the data set (e.g., that differs from acorresponding value in the reference data set). In some instances, asparse indicator may be defined based on identifying a type ofstructural difference detected in the data set relative to the referencedata set (e.g., duplication, insertion, inversion or deletion). In someinstances, an alignment is determined to be accurate throughout part ofthe data set but not for another part. It may then be determined thatsuch partial alignment is attributable to the data set, for example,lacking representation of a part of the reference sequence or having anadditional set of values. A sparse indicator may therefore identifyinformation corresponding to multiple positions (e.g., reflecting astart and stop of a part of a reference data set not represented in adata set or the converse) and/or multiple values (e.g., reflecting whichvalues were in one of either the reference data set or the data set butnot in the other).

In some instances, a state transition likelihood associated with aparticular deviation (e.g., sparse indicator) and/or with a combinationof deviations is unknown or is associated with a below-thresholdconfidence. With reference again to FIG. 1 and FIG. 2, upon detectingsuch a deviation or combination (or a threshold quantity thereof), theparticular deviation and/or combination may be identified in areview-request communication 265 and transmitted to an evaluation device170. Evaluation device 170 may then present the identification to anevaluator 175 and detect input that is indicative of an estimatedlikelihood to associate with the deviation and/or combination, forexample, as part of an optional review analysis process. Areview-request response 285 may be transmitted from evaluation device170 to assessment system 105, for example, to provide the results of anyreview or input generated by an evaluator 175. The data included inreview-request response 285 may be used in report generation process ofblock 290 and may be included and/or otherwise influence the content ofthe final report transmitted in report transmission 295.

A result generated by assessment system 105 may include a quantitativeor qualitative (e.g., categorical) likelihood variable, such as onecorresponding to a transitioning to a particular state. For example, thelikelihood variable may include a percentage probability or range oftransitioning into a particular state. As another example, thelikelihood variable may be partitioned into three categories.

Assessment system 105 may generate an electronic report, at block 290,that includes the result and/or that is selected based on the result. Areport communication or transmission 295 may include the report and betransmitted to client 125 or facility 120, such as by way of clientdevice 130 or requestor device 110 a. As an example, a report mayidentify one or more sparse indicators detected in a client data setand/or a bucket of each of one or more sparse indicator. A report mayidentify a likelihood (e.g., numeric or categorical) of transitioning toa particular state and/or a technique for having generated such aresult. A report may identify types of data (e.g., particular data-setunits and/or other type of data) used in the analysis. A report mayidentify a confidence in a result (e.g., a likelihood variable). Areport may identify a recommendation (e.g., to contact a requestor or toreceive a particular test or evaluation).

In some instances, a report must be approved (e.g., by a requestor 115 aor 115 b) before it is transmitted to a client device 130. Areport-reviewing interface may, but need not, include a configuration toallow a reviewing entity to change or add to the report. Areport-reviewing interface may further allow or require a reviewingentity to identify a time at which to send the report to a client.

Assessment system 105 may update and may have access to a variety ofdata stores, part or all of which may be remote from, co-localized withassessment system 105, and/or included in assessment system 105. One ormore of the data stores may include a relational data store, such thatdata from one data store or structure within a data store may be used toretrieve corresponding data from another data store or structure.

Each of one, more, or all of the data stores may be associated with oneor more access constraints. Access constraints applicable to a givendata store may be stored as part of the data store or separately (e.g.,in an access control data store). Access constraints that apply to onetype of data may differ from access constraints that apply to anothertype of data. For example, account and client data may be associatedwith stricter access constraints than results data, to make it moredifficult for a user, developer, or hacker to be able to link data to aparticular individual. An access constraint may identify one or moreindividuals, devices, systems, and/or occupations permitted to accesssome or all data in a data store. An access constraint may include arule, such as one that indicates that a user is permitted to access datapertaining to any of a group of users that the entity was involved inwith respect to a transfer of a kit, or that indicates that anylow-level authorized user is permitted to access de-identified data butnot identifiable data, or that indicates that a high-level authorizeduser is permitted to access all data. As another example, accessconstraints may indicate that process data is to be hidden from externaldevelopers and available to internal users; that data-set unit, sparseindicator, and data set availability data is to be made available to allauthorized external developers and internal users; and that client datais to be availed to authorized internal users and only availed toexternal developers to the extent to which each corresponding usersrepresented in the data is a user of the developer (e.g., and that theclient authorized such data access).

When different access rights apply to different types of data, a queryprotocol may be established to address instances where a query relatesto each type of data. For example, a query may request Variable X foreach client corresponding to Data Y, and Variable X and Data Y maycorrespond to different access constraints. As another example, a querymay request a count of clients for which both Data Y and Data Z weredetected, and Data Y and Z may correspond to different accessconstraints. One example of a query protocol is to use a mostrestrictive overlap of data constraints applying to the query. Anotherexample of a query protocol is to permit use of an at least partly morerelaxed access constraint so long as it relates to defining a client setor state and not to results to be returned or processed.

In some instances, an access constraint is configured to inhibit anidentification of particular data (e.g., client identity). Such aconstraint may relate to a precision of requested data. To illustrate, aconstraint may be configured to permit a user to request and receivedata identifying client locations, so long as the request is configuredto not request too specific of a location and/or so long as the requestcorresponds to a number of client data elements sufficiently large toobscure (e.g., in a statistical result) a precise location. Compoundqueries may be more sensitive to potential identification concerns, suchthat one or more access constraints are configured to permit access toless precise data when multiple data elements are being requested.

Various data stores may be included in assessment networks 100 and 300.The data stores may include, for example, an account data store 176,which may include login credentials for one or more users or clientsand/or types of data access to be granted to each user or client;process data store 177, which may identify facility analysischaracteristics pertaining to particular data elements (e.g.,identifying a facility, piece of equipment, and/or processing time);data sets data store 178, which may identify one or more data setsassociated with a given client or material, such as a sample; and one ormore data-set expressions or signatures associated with a given clientor material, such as a sample. The data stores may further oralternatively include a results data store 181, which may identify oneor more sparse indicators identified by and/or one or more resultsgenerated by assessment system 105 that are associated with a givenclient or material, such as a sample.

The data stores may further or alternatively include a reports datastore 182, which may include one or more report templates (e.g., eachassociated with one or more result types) and/or one or more reports tobe transmitted or having been transmitted to a client device; and/or arelevance support data store 183, which may identify which types of data(e.g., data-set units, full or partial reference data sets, activitypatterns, inputs, records, tests, etc.) are established to be,potentially, established not to be, or unknown whether to be relevantfor evaluating a particular type of likelihood (e.g., a likelihood oftransitioning into a particular state).

Relevance support data store 183 may include identifications of one ormore content objects. The identifications may include, for example, webaddresses, journal citations, or article identifiers. In some instances,an identification identifies one or more sources associated with thecontent object (e.g., scientist, author, journal, or data store).Content objects may be tagged with one or more tags, which may identify,for example, a sparse indicator, a data-set unit, a data set, and/or atype of assessment. In some instances, each of one or more contentobjects are associated with a score, which may reflect a credibility ofthe content object. The score may be based, for example, on apublication frequency of a source, an impact factor of a source, a dateof publication of the content object, and/or a number of citations tothe content object.

It will be appreciated that the illustrated data stores 155, 165, 176,177, 178, 181, 182, and 183 may each, independently and optionally, beincluded as a portion of data store 372, which may include a relationaldatabase, for example.

Assessment network 100 may also include a user device 180 configured todetect input from a user 185. User 185 may be associated with an accountor other authentication data indicating that access to some or all ofthe data is to be granted. Accordingly, user 185 may be able to interactwith various interfaces (presented at user device 180) to view datapertaining to one or more particular clients (e.g., in an identified orde-identified manner), to view summary data that relates to data frommultiple clients, to explore relationships between data types, and soon. In some instances, an interface may be configured to accept inputsfrom a user 185 so as to enable the user to request data pertaining to(for example) materials with sparse indicators in particular data-setunits, particular sparse indicators and/or state likelihoods.

In some instances, data is transmitted by assessment system 105 andreceived at user device 180. The transmitted data may relate todurations of work flow processing time periods. Specifically, as may beappreciated by disclosures included herein, generating outputs for usersand/or requestors may involve multiple steps, each of which may includea process, which may be referred to herein as a task, of an entityand/or device. Completion times of individual processes may then bemonitored and assessed. A work flow may include a structure anddefinition for these processes. For example, various work flows mayinclude some or all of the following tasks:

-   -   Inputs are collected at client device 130, transmitted by client        device 130, and received by assessment system 105, where the        inputs correspond to a preliminary request to conduct an        assessment based on a material and ensure that all required        inputs have been received;    -   A same or different client device 130 (e.g., a wearable device)        collects and transmits other data indicative of the client's        activity or status;    -   Inputs collected at requestor device 110 a, 110 b and        transmitted to assessment system 105 that correspond to a        request for assessment for the client;    -   Access control device 160 b at facility 120 collects and        transmits record data of the client;    -   Distribution device 135 receives alert corresponding to new        request and address information and confirms shipping of kit for        sample collection to the client;    -   Client 125 receives kit, collects material and sends to data        generator 140;    -   Assessment device(s) 145 collects data-set data, and access        control device 160 a sends facility data to assessment system        105;    -   Assessment system 105 detects any sparse indicators in data        set(s) and/or any modifications in data set expression;    -   Assessment system 105 assigns any sparse indicators and/or data        set availability modifications;    -   Evaluation device 170 collects inputs identifying an assignment        of any sparse indicators and/or data set availability        modifications as of an unknown likelihood;    -   Confirmatory facility testing of any sample associated with a        sparse indicator and/or data set availability modification        having a particular assignment at same or different facilities;    -   Assessment system 105 aggregates sparse indicator data,        assignment data, record data, user or client inputs, other data,        and/or activity or status data and generates one or more        likelihood variables;    -   Assessment system 105 generates electronic report with the one        or more likelihood variables;    -   Evaluation device 170 and/or requestor device 110 a collect        inputs indicating that the electronic report is approved for        transmission to client device 130; and    -   Assessment system 105 transmits the electronic report to client        device 130.

A work flow may include a task order that indicates that, for example, afirst task is to be completed prior to performance of a second task,though a work flow may alternatively be configured such that at leastsome tasks may be performed in parallel. In some instances, one or moretasks in a work flow are conditional tasks that need not be performedduring each iteration of the work flow. Rather, whether a conditionaltask is to be performed may depend on a circumstance, such as whether aresult from a prior task is of a particular type or exceeds a threshold.

Using a work flow, assessment system 105 may track timing of individualtasks during individual iterations of a work flow. Each iteration maycorrespond to generating a likelihood variable for a given client andmay involve various other entities (e.g., reviewers, facilities, etc.),which may be selected based on, for example, user preference, a physicallocation of a client device, and/or availability. For tasks performed atassessment system 105, timing may be directly determined. For tasksperformed by, at, and/or via another device, assessment system 105 maytrack timing via electronic transmissions between systems. For example,a start may be identified by an instruction communication sent fromassessment system 105 and/or a when a communication was receivedindicating that the corresponding task was beginning. As anotherexample, an end time may be identified by transmission of acommunication including a result of the corresponding task sent fromassessment system 105 and/or when a communication was receivedindicating that the corresponding task was complete.

FIG. 5 shows a representation of an embodiment of a process 500 forprocessing tasks in the assessment network 100. The process starts whenan event triggers a first work flow as shown at block 510. Any number ofevents occurring internal to the assessment network 100 and external tothe assessment network 100 may trigger a first work flow in any numberof ways. Each of the assessment system 105, a requestor device 110, aclient device 130, a distribution device 135, a facility data generator,an evaluation device 170, a user device 180, and an external assessmentdevice 190 may trigger a work flow, for example. For instance, theassessment system 105 may trigger a work flow when it receives anelectronic request 205. A requestor device 110 may trigger a work flowby transmitting electronic request 205. A user device may trigger a workflow based on inputs collected. A data generator 140 may trigger a workflow upon receipt of a sample. Other examples are possible and it willbe appreciated from the present description that any one or more datatransmissions between various devices and systems of assessment network100 may trigger a work flow. It will also be appreciated that variouswork flows may initiated sequentially or simultaneously, depending onthe particular need for completion of one work flow to complete beforeanother work flow may begin. In addition, additional work flows may betriggered while in the midst of processing one work flow. In someembodiments, an assessment system or assessment device manages and/orcoordinates triggered work flows. Optionally, task start times may betracked, as described above, and triggering a work flow may includetracking the start time of tasks associated with the work flow.

Some task work flows may require verification of permissions and/orauthorizations, such as depicted at block 515, before the work flow ispermitted to begin. For example, a transmission of record data of aclient may require explicit authorization from a client or a requestorbefore the transmission may begin, for example, due to the sensitivityof information that may be included in the record data. As anotherexample, transmission of information of a client to an externalassessment device may also require client permission. In this way,permission verification may prevent unanticipated or unauthorizedtransmission of information to a particular work flow processor forwhich such transmission may be undesirable. Timing of permission requestand verification may further be tracked, such as to allow identificationof bottlenecks in work flow and/or task processing associated withpermission verification. U.S. patent application Ser. No. 15/133,089,filed on Apr. 19, 2016 and U.S. Provisional Applications 62/150,218,filed on Apr. 20, 2016, and 62/274,660, filed on Jan. 4, 2016, disclosedetails regarding various work flow processes, and are each herebyincorporated by reference in its entirety for all purposes.

As illustrated in FIG. 5, if permissions are not verified, the work flowmay be stopped, at block 570. If permissions are verified, the work flowmay proceed to block 520. It will be appreciated that not all work flowsrequire permission verification, and so block 515 may be considered tobe optional.

Depending on the particular work flow initiated, the work flow requestmay require parsing, at block 520, to ensure that various portions ofthe work flow may be handled appropriately. Parsing may includedetermining that all required inputs, data, and/or materials needed forcompleting the work flow are available. In the event that additionalinputs, data, and/or materials are needed, the work flow may be returnedto the triggering device to request the additional inputs, data, and/ormaterials, for example. Parsing may also include aspects ofload-balancing. Parsing may also include, for example, analyzing thework flow request and associated data and/or materials to ensure thedata, materials and/or multiple individual sub-work flow processes aredirected to an appropriate work flow processor 535, 540, 545, 550, 555,etc. Task start times may optionally be tracked based on completion ofparsing a work flow request, for example.

In one embodiment, a work flow may correspond to performing a data setanalysis on a sample, which may include dividing the sample intosub-samples. The sub-samples may, for example, be redundantly analyzedto ensure accuracy. Parsing 520 may include identifying necessaryresources for completing a particular work flow.

After parsing the work flow request, the triggered work flow is started,at block 525. Optionally, synchronizer 530 oversees the processing ofindividual work flow processes by work flow processors. Optionally,tracked task start times may correspond to times at which the triggeredwork flow is actually passed to a work flow processor.

Some task work flows may include multiple individual work flowprocesses, such as a sequencing work flow for sequencing data-set unitdata or sparse indicator data from a sample, where each individual workflow process may correspond to, for example, one or more data sets.These individual work flow processes may be performed in series, forexample, such as if a particular work flow process requires input from aprevious work flow process. The individual work flow processes mayalternatively be performed in parallel, for example, if the separatework flow processes do not rely on an a result from another work flowprocess that may be performed simultaneously. Additionally, individualwork flow processes may be started and completed without regard to otherwork flow processes that may be operating. Upon a work flow processor535, 540, 545, 550, 555 completing the designated tasks, at 560, thework flow may be evaluated to determine whether the work flow iscompleted. If additional processing is required, the work flow mayreturn to synchronizer 530 for appropriate queuing. If no additionalprocessing is required, the work flow result may be forwarded asappropriate, at 565. Once a particular work flow is forwarded, the taskassociated with the work flow may stop, at block 570. Optionally, taskstop or end times may be tracked based on the time at which a work flowproceeds to stop at block 570.

Assessment system 105 may store task start and completion times, and/ortask completion time periods (i.e., a difference between correspondingtask completion and task start times) in process data store 177 inassociation with an identifier of the corresponding task and anidentifier of a corresponding work flow iteration (e.g., an identifierof a client or sample). Assessment system 105 may collect task start andcompletion times that correspond, for example, to a given time period,facility, user or client group, analysis type, etc. and analyze the dataat a population level. Through such analysis, assessment system 105 mayidentify average, median, or mode completion time periods for individualtasks so as to identify tasks, facilities, or entities associated withwork flow processing delay. Further or alternatively, assessment system105 may identify a backlog for individual tasks by identifying a numberof “open” tasks for which a start time has been identified but for whichno completion time is identified. Tasks, facilities, and/or entitiesassociated with high backlog may then be identified.

Such task completion time monitoring may be performed automaticallyand/or in response to a query communication from user device 180. Forexample, assessment system 105 may determine, for each handling entity(e.g., facility, distribution device, reviewer, or facility) a portionof tasks completed by a first threshold time identified for a giventask. Upon detecting that the portion exceeds a second threshold, analert communication may be transmitted to user device 180 and/or adevice of an associated entity. As another example, assessment system105 may present a statistic (e.g., mean) corresponding to a processingtime of each task in a work flow. The presentation may be interactive,such that more details about a statistic may be presented in response toa user selection of the statistic. For example, the statistic may bebroken down by entity and/or task start time period, or more detailedinformation (e.g., a distribution or list of start and completion times)may be presented.

In some instances, data transmitted from assessment system 105 to userdevice 180 may relate to data queries received from user device 180. Thequery may, in some instances, include one that specifically orimplicitly identifies one or more data-set units. For example,identification of a given kit or assessment may be associated with oneor more data-set units. Assessment system 105 may identify data that anyaccess constraints indicate are accessible to the user, and presenthigh-level population data. For example, assessment system 105 mayidentify a portion of clients for which any sparse indicator or aparticular sparse indicator was detected at each of the one or moredata-set units. Such data may be presented in an interactive manner,such that a user may select a represented portion of the data to drilldown into that data. For example, the interface may accept a selectionof a representation of each data-set unit, and the interface may beupdated to identify a distribution of particular sparse indicatorsdetected at the data-set unit.

A drill-down may be configured to, at some level, begin representingnon-data set data. For example, a selection of a particular sparseindicator or data-set unit may result in a display identifying adistribution of history data or demographic data from amongst clientsassociated with the particular sparse indicator or a sparse indicator atthe data-set unit. Thus, the drill-down may include retrieving data fromdifferent data stores depending on a level of precision. Further, eachstep in the drill-down may involve evaluating one or more applicableaccess constraints.

In some instances, a query may pertain to one or more data-set units,and query processing may include retrieving data (or results derivedtherefrom) and retrieving data set availability data (or results derivedtherefrom). For example, query processing may include identifying, foreach subject and for each of the one or more data-set units, whether asparse indicator or an data set availability modification was detected.A query result presentation may identify, for example, a portion ofsubjects for which a sparse indicator or modification was detected foreach of the data-set units and/or a query result presentation mayidentify, for each of the one or more data-set units, a portion ofsubjects or clients for which a particular type of sparse indicator ormodification was detected. The presentation may again be configured toaccept drill-down inputs so as to enable a user to further explore thepertinent data.

As another example, query processing may include identifying instancesin which, for a given client, both a sparse indicator (e.g., generallyor of a particular type) and an data set availability modification(e.g., generally or of a particular type) was detected (e.g., generally,at a particular data-set unit and/or at a particular position at adata-set unit).

Again with reference to FIG. 1, assessment network 100 may also includean external assessment device 190 configured to detect input from adeveloper 195. Via such inputs, external assessment device 190 may sendelectronic requests for data (e.g., relating to particular data-setunits, a particular user or client and/or particular user or clientinputs) to assessment system 105. The inputs may be received, forexample, via a webpage, application, or app page, which may identifygeneral types of data that is available for restricted access.Assessment system 105 may evaluate the request to determine, forexample, whether a corresponding client 125 authorized such access(which may be verified via a communication exchange between assessmentsystem 105 and client device 130) and/or whether such access is relevantto a purported type of analysis.

The evaluation may include assessing one or more permissions associatedwith a given user or client. In various instances, a permission may beset to be conditioned upon an entity or system transmitting a request, atype of data being requested, a size of data being requested, or apotential type of processing identified as being a use for the data. Forexample, a client may specify that an external assessment device may begranted access to data, such as data that includes data sets or sparseindicator detections, if the requested data pertains to fewer than afirst threshold number of data-set units, that access to data thatincludes sparse indicator detection may be granted if the requested datapertains to fewer than a second threshold number of data-set units, andthat access to the data is to be otherwise restricted.

Evaluation processing may depend, in part, on whether a system or entityassociated with a request has provided any data previously or presentlyand/or what type of data is being provided. For example, externalassessment devices and/or associated systems may provide data (e.g.,generated from an external facility and/or client sample), results data,input data, data set availability data, test data, and/or history data.

Evaluation processing may depend on one or more permissions orrestrictions associated with a request. The permissions or restrictionsmay be set, for example, based on client input, or lack thereof, and/orbased on which type of analysis and/or data storage was initially agreedto by a client. For example, an interface may be configured so as toenable a user or client to permit or restrict storage of particulartypes of data (e.g., data sets and/or sparse indicator detection beyondwhat is needed to perform a requested analysis), to permit or restrictsharing data to one or more other entities (e.g., generally, of a giventype or specific entities), and/or to permit or restrict using data toperform one or more other types of analyses. Permissions or restrictionspertaining to whether various analyses may be particularly importantgiven that rules or regulations may require particular results ofanalyses to be transmitted to a client. Thus, if such information is notdesired, analyses must be restricted.

In some instances, an interface may be configured to enable a user orclient to specify a degree of identification to be associated with dataof the client with regard to storage and/or distribution. For example, auser or client may be able to indicate that data and/or results are tobe associated with a pseudo-randomly generated unique identifier of theclient rather than client identifying information. As another example, aclient may be able to indicate that data is to be stored so as torequire a key for access, which may be held by the client. As anotherexample, a client may authorize transmission of the client's data toexternal assessment devices so long as identifying information of theclient (e.g., name, email, address, social security number, phonenumber, and so on) is not provided without subsequent explicitpermission.

In some instances, a same or different permission may be established toapply to other type of data (e.g., with regard to storage and/ordistribution), such as personal data, inputs and/or sensor data. In someinstances, a same or different permission may be established so as torelate to data collected from external systems. For example, apermission may indicate whether an assessment system is authorized torequest physician-system data (and/or what type of data), an externalassessment device-data, etc., and/or how an assessment is to handleresults provided by an external system.

If the evaluation indicates that access is to be granted, assessmentsystem 105 may, for example, send an instruction communication to datagenerator 140 to conduct a new analysis of an existing sample, send adata request to a device (e.g., access control device 160 b, clientdevice 130), and/or retrieve data from a data store (e.g., and extractpertinent information from any larger data structure, such as extractingdata-set unit-specific data from a reference data-set). When part or allof the data is accessible, one or more communications may be transmittedto the developer. The one or more meetings may include the data and/ormay include information (e.g., access credentials, login information, orftp IP address and credential information) to enable the developer toaccess the data. In some instances, other data different from that whichwas requested may be provided. The other data may include, for example,quality control metrics of the provided data, other data determined tobe relevant to an analysis, and/or other data that is being provided inlieu part or all of data that had been requested.

Various devices in assessment network 100 may communicate with one ormore other devices in assessment network 100 via a network, such as acommunication system, the Internet, a local-area network, or ashort-range network. Communications may be sent in a secure manner to,e.g., inhibit unauthorized access to health-record data. Techniques suchas token authentication and/or encryption may be used.

It will be appreciated that the representations of devices andconfigurations depicted in FIGS. 1, 2, and 3 are illustrative. Forexample, while a single data generator 140, client device 130, and datastores 178, etc., are shown, a system may include multiple datagenerators 140, client devices 130, data store 178, etc. As anotherexample, while access control devices 160 a, 160 b are shown as beingconnected to data store 155 and record data store 165, additional accesscontrol devices may be present in assessment network 100. For example,an access control device may be included within or connected toassessment system 105 so as to control access that requestor device 110b, client device 130, distribution device 135, evaluation device 170,user device 180 and/or external assessment device 190 may achieve.

With reference now to FIG. 6, a block diagram of an illustrativeassessment network device 600 is shown. The device 600 may correspond toany of the devices or systems of the assessment network 100 describedabove, or any other computing devices described herein, and specificallymay include, for example, one or several of an assessment system 105, arequestor device 110, a client device 130, a distribution device 135, anassessment device 145, a technician device 150, an access control device160 a, a reviewer or user device 180, an external assessment device 190,external system 249, data-characterizer device 410, data set analyzer420, and/or any of the work flow processors 535, 540, 545, 550, and 555.Aspects of device 600 may further be incorporated in one or more of datastores 155, 165, 176, 177, 178, 181, 182, 183, 415, 425, and 430 anddata store 372. It will be appreciated that each of the devices referredto that may correspond to an instance of device 600 may be independentand unique from all other instances of device 600 and may include feweror additional components as those illustrated in FIG. 6.

In the example illustrated in FIG. 6, device 600 includes processingunits 604 that communicate with a number of peripheral subsystems via abus subsystem 602. These peripheral subsystems include, for example, astorage subsystem 610, an I/O subsystem 626, and a communicationssubsystem 632.

Bus subsystem 602 provides a mechanism for letting the variouscomponents and subsystems of device 600 communicate with each other.Although bus subsystem 602 is shown schematically as a single bus,alternative embodiments of the bus subsystem may utilize multiple buses.Bus subsystem 602 may be any of several types of bus structuresincluding a memory bus or memory controller, a peripheral bus, and alocal bus using any of a variety of bus architectures. Sucharchitectures may include, for example, an Industry StandardArchitecture (ISA) bus, Micro Channel Architecture (MCA) bus, EnhancedISA (EISA) bus, Video Electronics Standards Association (VESA) localbus, and Peripheral Component Interconnect (PCI) bus, which may beimplemented as a Mezzanine bus manufactured to the IEEE P1386.1standard.

Processing unit 604, which may be implemented as one or more integratedcircuits (e.g., a conventional microprocessor or microcontroller),controls the operation of device 600. Processing unit 604 may beimplemented as a special purpose processor, such an application-specificintegrated circuit, which may be customized for a particular use and notusable for general-purpose use. One or more processors, including singlecore and/or multicore processors, may be included in processing unit604. As shown in FIG. 6, processing unit 604 may be implemented as oneor more independent processing units 606 and/or 608 with single ormulticore processors and processor caches included in each processingunit. In other embodiments, processing unit 604 may also be implementedas a quad-core processing unit or larger multicore designs (e.g.,hexa-core processors, octo-core processors, ten-core processors, orgreater).

Processing unit 604 may execute a variety of software processes embodiedin program code, and may maintain multiple concurrently executingprograms or processes. At any given time, some or all of the programcode to be executed may be resident in processor(s) 604 and/or instorage subsystem 610. In some embodiments, device 600 may include oneor more specialized processors, such as digital signal processors(DSPs), outboard processors, graphics processors, application-specificprocessors, and/or the like.

I/O subsystem 626 may include device controllers 628 for one or moreuser interface input devices and/or user interface output devices 630.User interface input and output devices 630 may be integral with device600 (e.g., integrated audio/video systems, and/or touchscreen displays),or may be separate peripheral devices which are attachable/detachablefrom device 600. The I/O subsystem 626 may provide one or severaloutputs to a user by converting one or several electrical signals touser perceptible and/or interpretable form, and may receive one orseveral inputs from the user by generating one or several electricalsignals based on one or several user-caused interactions with the I/Osubsystem such as the depressing of a key or button, the moving of amouse, the interaction with a touchscreen or trackpad, the interactionof a sound wave with a microphone, or the like.

Input devices 630 may include a keyboard, pointing devices such as amouse or trackball, a touchpad or touch screen incorporated into adisplay, a scroll wheel, a click wheel, a dial, a button, a switch, akeypad, audio input devices with voice command recognition systems,microphones, and other types of input devices. Input devices 630 mayalso include three dimensional (3D) mice, joysticks or pointing sticks,gamepads and graphic tablets, and audio/visual devices such as speakers,digital cameras, digital camcorders, portable media players, webcams,image scanners, fingerprint scanners, barcode reader 3D scanners, 3Dprinters, laser rangefinders, haptic devices, and eye gaze trackingdevices. Additional input devices 630 may include, for example, motionsensing and/or gesture recognition devices that enable users to controland interact with an input device through a natural user interface usinggestures and spoken commands, eye gesture recognition devices thatdetect eye activity from users and transform the eye gestures as inputinto an input device, voice recognition sensing devices that enableusers to interact with voice recognition systems through voice commands,medical imaging input devices, MIDI keyboards, digital musicalinstruments, and the like.

Output devices 630 may include one or more display subsystems, indicatorlights, or non-visual displays such as audio output devices, etc.Display subsystems may include, for example, cathode ray tube (CRT)displays, flat-panel devices, such as those using a liquid crystaldisplay (LCD) or plasma display, light-emitting diode (LED) displays,projection devices, touch screens, haptic devices, and the like. Ingeneral, use of the term “output device” is intended to include allpossible types of devices and mechanisms for outputting information fromdevice 600 to a user or other computer. For example, output devices 630may include, without limitation, a variety of display devices thatvisually convey text, graphics and audio/video information such asmonitors, printers, speakers, headphones, automotive navigation systems,plotters, voice output devices, and modems.

Device 600 may comprise one or more storage subsystems 610, comprisinghardware and software components used for storing data and programinstructions, such as system memory 618 and computer-readable storagemedia 616. The system memory 618 and/or computer-readable storage media616 may store program instructions that are loadable and executable onprocessing units 604, as well as data generated during the execution ofthese programs. Program instructions may include instructions to performone or more actions or part(s) or all of one or more methods orprocesses described herein. For example, program instructions mayinclude instructions for identifying and/or aligning sparse indicators.Program instructions may include instructions for generating,transmitting, and/or receiving communications. Program instructions mayinclude instructions for automated processing. Program instructions mayinclude instructions for generating automated processing and/or stageresults. Program instructions may include instructions for performing awork flow iteration.

Depending on the configuration and type of device 600, system memory 618may be stored in volatile memory (such as random access memory (RAM)512) and/or in non-volatile storage drives 614 (such as read-only memory(ROM), flash memory, etc.) The RAM 612 may contain data and/or programmodules that are immediately accessible to and/or presently beingoperated and executed by processing units 604. In some implementations,system memory 618 may include multiple different types of memory, suchas static random access memory (SRAM) or dynamic random access memory(DRAM). In some implementations, a basic input/output system (BIOS),containing the basic routines that help to transfer information betweenelements within device 600, such as during start-up, may typically bestored in the non-volatile storage drives 614. By way of example, andnot limitation, system memory 618 may include application programs 620,such as user applications, Web browsers, mid-tier applications, serverapplications, etc., program data 622, and an operating system 624.

Storage subsystem 610 also may provide one or more tangiblecomputer-readable storage media 616 for storing the basic programmingand data constructs that provide the functionality of some embodiments.Software (programs, code modules, instructions) that when executed by aprocessor provide the functionality described herein may be stored instorage subsystem 610. These software modules or instructions may beexecuted by processing units 604. Storage subsystem 610 may also providea repository for storing data used in accordance with the presentinvention.

Storage subsystem 610 may also include a computer-readable storage mediareader that may further be connected to computer-readable storage media616. Together and, optionally, in combination with system memory 618,computer-readable storage media 616 may comprehensively representremote, local, fixed, and/or removable storage devices plus storagemedia for temporarily and/or more permanently containing, storing,transmitting, and retrieving computer-readable information.

Computer-readable storage media 616 containing program code, or portionsof program code, may include any appropriate media known or used in theart, including storage media and communication media, such as but notlimited to, volatile and non-volatile, removable and non-removable mediaimplemented in any method or technology for storage and/or transmissionof information. This may include tangible computer-readable storagemedia such as RAM, ROM, electronically erasable programmable ROM(EEPROM), flash memory or other memory technology, CD-ROM, digitalversatile disk (DVD), or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or other tangible computer readable media. This may also includenontangible computer-readable media, such as data signals, datatransmissions, or any other medium that may be used to transmit thedesired information and that may be accessed by device 600.

By way of example, computer-readable storage media 616 may include ahard disk drive that reads from or writes to non-removable, nonvolatilemagnetic media, a magnetic disk drive that reads from or writes to aremovable, nonvolatile magnetic disk, and an optical disk drive thatreads from or writes to a removable, nonvolatile optical disk such as aCD ROM, DVD, and Blu-Ray disk, or other optical media. Computer-readablestorage media 616 may include, but is not limited to, Zip drives, flashmemory cards, universal serial bus (USB) flash drives, secure digital(SD) cards, DVD disks, digital video tape, and the like.Computer-readable storage media 616 may also include, solid-state drives(SSD) based on non-volatile memory such as flash-memory based SSDs,enterprise flash drives, solid state ROM, and the like, SSDs based onvolatile memory such as solid state RAM, dynamic RAM, static RAM,DRAM-based SSDs, magnetoresistive RAM (MRAM) SSDs, and hybrid SSDs thatuse a combination of DRAM and flash memory based SSDs. The disk drivesand their associated computer-readable media may provide non-volatilestorage of computer-readable instructions, data structures, programmodules, and other data for device 600.

Communications subsystem 632 may provide a communication interface fromdevice 600 and remote computing devices via one or more communicationnetworks, including local area networks (LANs), wide area networks(WANs) (e.g., the Internet), and various wireless telecommunicationsnetworks. As illustrated in FIG. 6, the communications subsystem 632 mayinclude, for example, one or more network interface controllers (NICs)634, such as Ethernet cards, Asynchronous Transfer Mode NICs, Token RingNICs, and the like, as well as one or more wireless communicationsinterfaces 638, such as wireless network interface controllers (WNICs),wireless network adapters, and the like. Additionally and/oralternatively, the communications subsystem 632 may include one or moremodems (telephone, satellite, cable, ISDN), synchronous or asynchronousdigital subscriber line (DSL) units, FireWire interfaces, USBinterfaces, and the like. Communications subsystem 632 also may includeradio frequency (RF) transceiver components for accessing wireless voiceand/or data networks (e.g., using cellular telephone technology,advanced data network technology, such as 3G, 4G or EDGE (enhanced datarates for global evolution), Wi-Fi (IEEE 802.11 family standards, orother mobile communication technologies, or any combination thereof),global positioning system (GPS) receiver components, and/or othercomponents.

The various physical components of the communications subsystem 632 maybe detachable components coupled to the device 600 via a computernetwork, a FireWire bus, a serial bus, or the like, and/or may bephysically integrated onto a motherboard or circuit board of device 600.Communications subsystem 632 also may be implemented in whole or in partby software.

In some embodiments, communications subsystem 632 may also receive inputcommunication in the form of structured and/or unstructured data feeds,event streams, event updates, and the like, on behalf of one or moreusers who may use or access device 600. For example, communicationssubsystem 632 may be configured to receive data feeds in real-time fromother communication services, web feeds such as Rich Site Summary (RSS)feeds, and/or real-time updates from one or more third party informationsources. Additionally, communications subsystem 632 may be configured toreceive data in the form of continuous data streams, which may includeevent streams of real-time events and/or event updates (e.g., data setcompletion, results transmission, other data transmission, reporttransmission, etc.). Communications subsystem 632 may output suchstructured and/or unstructured data feeds, event streams, event updates,and the like to one or more data stores that may be in communicationwith device 600.

Due to the ever-changing nature of computers and networks, thedescription of device 600 depicted in FIG. 6 is intended only as aspecific example. Many other configurations having more or fewercomponents than the device depicted in the figure are possible. Forexample, customized hardware might also be used and/or particularelements might be implemented in hardware, firmware, software, or acombination. Further, connection to other computing devices, such asnetwork input/output devices, may be employed. Based on the disclosureand teachings provided herein, it will be appreciated that there areother ways and/or methods to implement the various embodiments.

With reference now to FIG. 7, a diagram of components of an illustrativeassessment network device 700 is shown. The device 700 may correspond toany of the devices or systems of the assessment network 100 describedabove, or any other computing devices described herein, and specificallymay include, for example, one or several of an assessment system 105, arequestor device 110, a client device 130, a distribution device 135, anassessment device 145, a technician device 150, an access control device160 a, a reviewer or user device 180, an external assessment device 190,external system 249, data-characterizer device 410, data set analyzer420, any of the work flow processors 535, 540, 545, 550, and 555, and/ordevice 600. Aspects of device 700 may further be incorporated in one ormore of data stores 155, 165, 176, 177, 178, 181, 182, 183, 415, 425,and 430, and data store 372. It will be appreciated that each of thedevices referred to that may correspond to an instance of device 700 maybe independent and unique from all other instances of device 700 and mayinclude fewer or additional components as those illustrated in FIG. 7.

Various components may be included in device 700. Components may includesome or all of the following: a network interface 702 (which may operatein or function as a link layer of a protocol stack), a message processor704 (which may operate in or function as a network layer of a protocolstack), a communications manager 706 (which may operate in or functionas a transport layer of a protocol stack), a communications configurer708 (which may operate in or function as a portion of transport and/ornetwork layer in a protocol stack), a communications rules provider 710(which may operate in or function as part of a transport and/or networklayer in a protocol stack), and applications 712 (which may operate inor function as an application layer of a protocol stack).

Network interface 702 receives and transmits messages via one or morehardware components that provide a link-layer interconnect. The hardwarecomponents associated with network interface 702 may include, forexample, a radio frequency (RF) antenna or a port (e.g., Ethernet port)and supporting circuitry. In some embodiments, network interface 702 maybe configured to support wireless communication, e.g., using Wi-Fi (IEEE802.11 family standards), Bluetooth, or other wireless communicationsstandards.

The RF antenna, if present, may be configured to convert electricsignals into radio and/or magnetic signals (e.g., to radio waves) totransmit to another device and/or to receive radio and/or magneticsignals and convert them to electric signals. RF antenna may be tuned tooperate within a particular frequency band. In some instances, device700 includes multiple antennas, and the antennas may be, for example,physically separated. In some instances, antennas differ with respect toradiation patterns, polarizations, take-off angle gain and/or tuningbands. Network interface 702 may include one or more phase shifters,filters, attenuators, amplifiers, switches and/or other components todemodulate received signals, coordinate signal transmission, and/orfacilitate high-quality signal transmission and receipt using the RFantenna.

In some instances, network interface 702 includes a virtual networkinterface, so as to enable the device to utilize an intermediate devicefor signal transmission or reception. For example, network interface 702may include or utilize virtual private networking (VPN) software.

Network interface 702 may be configured to transmit and receive signalsover one or more connection types. For example, network interface may beconfigured to transmit and receive Wi-Fi signals, Ethernet signals,cellular signals, Bluetooth signals, etc.

Message processor 704 may coordinate communication with other electronicdevices or systems, such as one or more user devices, requestor devices,assessment systems, data stores, assessment devices, distributiondevice, reviewer device, etc. In one instance, message processor 704 isable to communicate using a plurality of protocols (e.g., any known,future and/or convenient protocol such as, but not limited to, internetprotocol (IP), short message service, (SMS), multimedia message service(MMS), etc.). Message processor 704 may further optionally serializeincoming and/or outgoing messages and facilitate queuing of incoming andoutgoing message traffic.

Message processor 704 may perform functions of an Internet or networklayer in a network protocol stack. For example, in some instances,message processor 704 may format data packets or segments, combine datapacket fragments, fragment data packets and/or identify destinationapplications and/or device addresses. For example, message processor 704may defragment and analyze an incoming message to determine whether itis to be forwarded to another device and, if so, may address andfragment the message before sending it to the network interface 702 tobe transmitted. As another example, message processor 704 may defragmentand analyze an incoming message to identify a destination applicationthat is to receive the message and may then direct the message (e.g.,via a transport layer) to the application.

Communications manager 706 may implement transport-layer functions. Forexample, communications manager 706 may identify a transport protocolfor an outgoing message (e.g., transmission control protocol (TCP) oruser diagram protocol (UDP)) and appropriately encapsulate the messageinto transport protocol data units. Message processor 704 may initiateestablishment of connections between devices, monitor transmissionsfailures, control data transmission rates, and monitor transmissionquality. As another example, communications manager 706 may read aheader of an incoming message to identify an application layer protocolused to receive the message's data. The data may be separated from theheader and sent to the appropriate application. Message processor 704may also monitor the quality of incoming messages, detect out of orderincoming packets, detect missing packets, reorder out of order packets,request retransmission of missing packets, request retransmission of outof order packets, etc.

In some instances, characteristics of message-receipt ormessage-transmission quality may be used to identify a quality status ofan established communications link. In some instances, communicationsmanager 706 may be configured to detect signals indicating the stabilityof an established communications link (e.g., a periodic signal from theother device system, which if received without dropouts, indicates astable link).

In some instances, a communication configurer 708 is provided to trackattributes of another system so as to facilitate establishment of acommunication session. In one embodiment, communication configurer 708further ensures that inter-device communications are conducted inaccordance with the identified communication attributes and/or rules.Communication configurer 708 may maintain an updated record of thecommunication attributes of one or more devices or systems. In oneembodiment, communications configurer 708 ensures that communicationsmanager 706 may deliver the payload provided by message processor 704 tothe destination (e.g., by ensuring that the correct protocolcorresponding to the receiving system is used). Optionally,communications configurer 708 may reformat, encapsulate, or otherwisemodify the messages directed to the message processor 704 to ensure thatthe message processor 704 is able to adequately facilitate transmissionof the messages to their ultimate destination.

A communications rules provider 710 may implement one or morecommunication rules that relate to details of signal transmissions orreceipt. For example, a rule may specify or constrain a protocol to beused, a transmission time, a type of link or connection to be used, adestination device, and/or a number of destination devices. A rule maybe generally applicable or conditionally applicable (e.g., only applyingfor messages corresponding to a particular app, during a particular timeof day, while a device is in a particular geographical region, when ausage of a local device resource exceeds a threshold, etc.). Forexample, a rule may identify a technique for selecting between a set ofpotential destination devices based on attributes of the set ofpotential destination devices as tracked by communication configure 708.To illustrate, a device having a short response latency may be selectedas a destination device. As another example, communications rulesprovider 710 may maintain associations between various devices orsystems and resources. Thus, messages corresponding to particularresources may be selectively transmitted to destinations having accessto such resources.

A variety of applications 712 may be configured to initiate messagetransmission, process incoming transmissions, facilitate permissionsrequests for access to protected data, facilitate automatic access toprotected data, facilitate task work flow permission verification,and/or performing other functions. In the instance depicted in FIG. 7,application modules 712 include a data viewer application 714, a dataanalyzer application 716, and/or a permission control application 718.It will be appreciated that the application modules depicted in FIG. 7are merely examples and other example application modules are include,but are not limited to, one that is associated with aspects of part orall of each of one or more actions, methods, and/or processes disclosedherein.

Data stores 722 may store data for use by application modules 712, asnecessary, and may include, for example, generated data store 724,account data store 726, sparse indicator data store 728, and reportsdata store 730. Optionally, data store 372 may be included in datastores 722. It will be appreciated that fewer or more or different datastores than those illustrated in FIG. 7 may be included in data stores722, such as any one or more of data stores 155, 165, 176, 177, 178,181, 182, and 183 depicted in FIG. 1.

One or more of data stores 724, 726, 728, and 730 may be a relationaldata store, such that elements in one data store may be referencedwithin another data store. For example, account data store 726 mayassociate an identifier of a particular account with an identifier of aparticular user or client. Additional information about the user maythen be retrieved by looking up the account identifier in sparseindicator data store 728, for example.

The components illustrated in FIG. 7 may be useful for establishing datacommunications and exchanging data between various other systems. Forexample, independent instances of device 700 may represent the requestordevice 110 and the assessment system 105 illustrated in FIGS. 1 and 2.Other examples are possible.

As an example, data analyzer application 716 may perform alignment ofdata sets, request reference data, determine sparse indicators,determine scores, determine buckets, etc. Such actions may be performedin response to messages received by device 700 from another instance ofdevice 700. If data that is unavailable locally in device 700 is neededby an application module 712, a request may be transmitted by device700, first by generating the request, forwarding the request tocommunications manager 706, which then may process and modify therequest as necessary for subsequent handling by message processor 704.In turn, message processor 704 may process and modify the request asnecessary, such as by adding header and/or footer information, forsubsequent handling by network interface 702. Network interface 702 maythen perform further processing and modification of the request, such asby adding additional header and/or footer information, and thenfacilitate transmission of the request to a remote system, such as anexternal system that may possess the needed data.

Referring next to FIG. 8, a representation of a system 800 for assigningsparse indicators to data buckets is shown, such as by performing a workflow iteration(s), performing automated processing for stage(s),generating stage result(s) from one or more stages of a work flow, andanalyzing data buckets. System 800 may represent portions of assessmentsystem 105 and may, for example, include portions of data generator 140.System 800 may be in data communication with one or more othercomponents of assessment network 100 or 300, such as client device 130and data store 372, for example.

System 800 includes an assessment device 815, which may be used toanalyze and/or compare generated data 805 with reference data 810 togenerate a data stream 820, which may include one or more sparseindicators 820A, 820B, 820C, 820D, etc. Thus, it will be appreciatedthat data 805 may include data aligned with a portion of a referenceset, such that individual values of data 805 may be compared tocorresponding values in reference data 810. In some embodiments,multiple individual data sets are obtained for a particular client and acompiled data set may be assembled from alignments of a plurality of theindividual data sets. The compiled data set may be compared with one ormore reference data sets or a compiled reference data set to identifysparse indicators associated with the compiled data set for theparticular client. It will also be appreciated that generated data 805may include identifier data and coverage data that may be used byassessment device 815 in generating data stream 820, such as bycomparing identifier data with reference data 810 and using coveragedata in tandem to determine a type, identity, value, and/or confidencemetric associated with a sparse indicator in data stream 820.

Different types of sparse indicators may be identified, such as aone-element sparse indicator representing a single data elementdifferent from a reference data set, or a clustered sparse indicatorrepresenting a set of consecutive data elements different from areference data set. A clustered sparse indicator may be detected upondetermining (for example) that a series of elements in a data setgenerally differ from those in a reference data set or that values in acoverage set change across the set so as to indicate that a portion ofthe reference data set is over- or underrepresented in the data set.Thus, in some instances, a reference set may include a referencecoverage set. Although only four sparse indicators 820A-820D aredepicted as part of data stream 820, it will be appreciated that more orfewer sparse indicators may be identified for a particular set ofgenerated data and that the four sparse indicators 820A-820D are merelyexamples.

System 800 further includes a look-up engine 830, which may determinewhether each individual sparse indicator corresponds tobucket-assignment data in stored data 825 (e.g., a look-up table). Forexample, a look-up table may include a set of entries, each of whichcorresponds to a sparse indicator. A sparse indicator may be identified(for example) by a position and identifier or by a range of positionsand type of sparse identifier (e.g., type of structural sparseidentifier and/or one or more corresponding position ranges in areference data set). For example, FIG. 8 illustrates stored data 825arranged in a table or array, such that a value along a first dimensioncan represent an identifier detected in a client data set and a valuealong a second dimension can represent a position at which theidentifier was detected. Elements that correspond to those in areference data set need not have a value. Each of one or more otherelements may include bucket-assignment data, which may identify a bucketto which the sparse indicator is to be assigned and, in some instances,a confidence of such assignment. In some instances, one or more elementsindicate that bucket-assignment data is not yet available).

The depicted stored data 825 may be useful for identifyingbucket-assignment data for sparse indicators corresponding todifferences between a client data set and reference data set atindividual positions. It will be appreciated that additional stored data825 may identify bucket-assignment for other types of sparse indicators(e.g., structural sparse indicators), such as a sparse indicator thatindicates that elements from Position X to Position Y are not present ina client data set.

If a look-up of a particular sparse indicator is successful, look-upengine 830 may proceed to assign the sparse indicator in accordance withthe bucket-assignment data. If a look-up of the particular sparseindicator is not successful or if a work flow calls for additionalstages, the information associated with the sparse indicator and/or theresult(s) from the look-up may be directed to data processor 840.

Look-up engine 830 may further allow for filtering of sparse indicators,such as to determine when a reviewer-assisted analysis of a particularsparse indicator is not needed or not to be performed. For example, somesparse indicators may be pre-assigned to particular data bucket(s) andlook-up engine may identify these sparse indicators as such. In anotherexample, some sparse indicators may not be suitable for an iterativeanalysis and/or may be predetermined such that no resources are to beused in analyzing the sparse indicator. For example, some sparseindicators are associated with a position in a full data set for whichanalysis is determined to be unnecessary. Optionally, some sparseindicators are associated with a position in a full data set and valuefor which analysis is determined to be unnecessary.

System 800 further includes a data processor 840, which may performiterative performance of automated processing for each of the sparseindicators in data stream 820. It will be appreciated that more dataprocessors 840 may be included in system 800, such as to allow paralleland/or sequential work flow performance. Data processor 840 may performfully automated processing of stages of a work flow and forward stageresult(s) to bucketor 855 for data bucket assignment.

In some embodiments of automated processing for one or more sparseindicators, data processor 840 may encounter one or more stages having astage-progression condition that is not satisfied or may determine thata reviewer-engagement condition is satisfied (e.g., due to a failure toidentify a bucket for a sparse indicator in a look-up data store or dueto determining that a bucket assignment for a sparse indicator isassociated with a confidence metric that is below a predefinedquantitative or qualitative threshold). Optionally, data processor 840may generate and transmit a query communication 845 that includes one ormore of a position associated with a sparse indicator, one or morevalues associated with the sparse indicator, and a result(s) from aprevious stage of the work flow. The query communication 845 may betransmitted, for example, from system 800 to an evaluation device 170 tofacilitate review and/or input by evaluator 175. For example, evaluationdevice 170 may receive the query communication 845 and display theincluded information to allow the evaluator 175 to provide response datato satisfy the stage-progression condition. Evaluation device 170 maythen generate a response communication 850 that includes response data.Data processor 840 may receive response communication 850 and use theincluded response data to complete or augment the automated processingto generate stage result(s). Once the stages are completed according tothe work flow, stage result(s) may be forward to bucketor 855.

System 800 further includes bucketor 855, which may assign each sparseindicator to a bucket of a plurality of data buckets, such as by usingstage result(s) from data processor 840 and/or look-up result(s) fromlook-up engine 830. Bucketor 855 may then assign a particular databucket for the particular sparse indicator being analyzed. It will beappreciated that more bucketors 855 may be included in system 800. Insystem 800, five data buckets 860, 862, 864, 866, and 868 are depicted,though it will be appreciated that more or fewer data buckets may beutilized. Some or all of data buckets 860-868 may, for example, span arange along a spectrum of a degree of likeliness that a client willtransition into or experience a particular state. Upon full or partialcompletion of the assignment of the sparse indicators in data stream 820to data buckets, information may be passed to bucket assessor 870. Itwill be appreciated that counts assigned to a set of buckets may bedetermined with respect to each of multiple position ranges (or units)or combinations thereof. For example, for a given data set, a count maybe generated for each of a set of buckets and for each of a set of unitsthat reflects a number of sparse indicators detected for the unit thatcorrespond to the bucket.

System 800 further includes bucket assessor 870. Although bucketassessor 870 is shown schematically as a separate component frombucketor 855, it will be appreciated that bucket assessor 870 andbucketor 855 may be combined in a single component or process. Bucketassessor 870 may identify a number of sparse indicators assigned toparticular buckets 860-868 using one or more counters, for example.Bucket assessor 870 may optionally determine whether one or more bucketsinclude counts above a predetermined threshold (e.g., whether a countexceeds zero). The predetermined threshold may be (for example) definedby a user, generated based on machine learning, generated based on avirtual structural representor, and/or generated based on a populationanalysis. For example, in one instance, it may be determined whether acount in a given bucket or a total count across a combination of buckets(e.g., a bucket corresponding to a highest predicted likelihood, amongstthe buckets, of transitioning into or being in a particular state or twobuckets corresponding to the two highest predicted likelihoods) exceedszero. It will be appreciated that predetermined thresholds for each databucket may be independent of other predetermined thresholds. Bucketassessor 870 may forward the counts corresponding to the buckets 860-868to signal generator 875.

A signal generator 875 may use the counts and/or results of a thresholdcomparison, for example, to generate a communication 880 indicative ofwhether a number of sparse indicators assigned to particular databuckets exceed the predetermined threshold(s). In some embodiments,different templates for communication 880 may be used depending on whichdata bucket(s) exceed the predetermined threshold(s) and or by how mucha threshold(s) is exceeded, for example. Communication 880 may identify,for example, whether one or more sparse indicators are assigned to abucket representing a highest probability, amongst the buckets, oftransitioning into or being at a particular state. Communication 880 mayidentify, for example, whether one or more sparse indicators areassigned to each of one or more other buckets.

Referring next to FIG. 9, a representation of a system 900 for analyzingsparse indicator information and sensor data is shown. System 900 mayrepresent portions of assessment network 100 or 300 and may, forexample, include additional or fewer elements than indicated in FIG. 9.System 900 may be in data communication with one or more othercomponents of assessment network 100 or 300 not shown in FIG. 9, such asrequestor device 110 a or 110 b, one or more facilities 120, one or moredata generators 140, and/or one or more data stores 372, for example.

System 900 includes an assessment system 905 and client device 910.Client device 910 may generate and transmit an analysis request 915 toassessment system 905 to initialize determination of a status analysisfor a client using sparse indicator information associated with theclient and sensor data associated with the client. Analysis request 915may be received at a data processor 920 of assessment system 905. Dataprocessor 920 may query a data store 925 to obtain the sparse indicatorinformation associated with the client. It will be appreciated that dataprocessor 920 may first determine an identifier associated with theclient in order to obtain the sparse indicator information associatedwith the client from the data store 925.

Assessment system 905 may also receive data from one or more sensors 930associated with the client, such as at data processor 920, for use inthe assessment analysis. For example, the sensor data may correspond toenvironmental sensor data, chemical sensor data, and/or motion oraccelerometer data that may impact an analysis of a likelihooddetermination for a client transitioning to a particular state, forexample.

Sensor data may also include information about or indicative of acurrent quality (e.g., a state, or condition) of a client or may be usedto determine a current quality of a client. For example, the sensor datamay provide or correspond to a marker or indicator identifying a currentquality of a client, such as an indication of whether a particularmarker is present or absent in a fluid associated with a client, such asa hormone, metabolite, chemical, structure, toxin, protein, etc. Thesensor data may optionally be quantitative and the associated qualitymay also relate to a level or degree or amount of the marker detected.The quality may relate to, for example, a range of progression of astate or condition. In some embodiments, the sensor data may be comparedwith one or more thresholds indicating different quality levels and thecurrent quality of the client may be assigned to a particular qualitylevel based on the sensor data.

Sensor data may be used in the assessment analysis in a variety of ways.As one example, the sensor data may be used to estimate exposure of theclient to a particular element, and this exposure may have a knownassociation with a higher or lower likelihood of transitioning to aparticular state and therefore impact the generated likelihood for aclient transitioning to the particular state. Optionally, a currentquality of a client may relate to a higher or lower likelihood oftransitioning to a particular state and therefore impact the generatedlikelihood for a client transitioning to the particular state. In someembodiments, the data processor 920 may compute a first likelihood usingonly the sparse indicator information and also compute a secondlikelihood using both the sparse indicator information and the sensordata. The data processor 920 may also compute a change in likelihoodbetween the first likelihood and the second likelihood, which may beattributable, at least in part, to the sensor data. Continued readingsor receipt of sensor data may allow for updated likelihoods to bedetermined.

Sensors 930 may optionally be integrated directly into client device910. Example sensors associated with the client are depicted in FIG. 9.For example, client device 910 may include one or more air qualitysensors 931, pressure sensors, 932, humidity sensors 933, generalsensors 934, light sensors 935, temperature sensors 936, acceleration ormotion sensors 937, vibration sensors 938, or rotation sensors 939. Itwill be appreciated that general sensor 934 may represent any othersensor not specifically described here that may be incorporated intoclient device 910 and that more or fewer sensors may be incorporatedinto client device 910. Optionally, sensor data from the one or moresensors of client device 910 may be communicated to assessment system905 by inclusion in analysis request 915. Optionally, sensor data fromthe one or more sensors of client device 910 may transmitted separately.For example, sensor data may be pushed to assessment system 905 directlyby client device 910. As another example, sensor data may be pulled byassessment system 905, such as by way of one or more query/responsecommunication exchanges.

System 900 may also include a standalone sensor device 940 that may alsoprovide sensor data to assessment system 905 data processor 920. As anexample, standalone sensor device 940 illustrated in FIG. 9 may includeone or more general sensors 941, smoke and/or particulate sensors 942,and chemical sensors 943. It will be appreciated that more or fewersensors may be included in standalone sensor device 940 and that generalsensor 941 may represent any other sensor or sensor type that may beincorporated into a standalone sensor device 940. It will further beappreciated that multiple and/or different standalone sensor devices 940may be incorporated into system 900.

Standalone sensor device 940 may also provide sensor data to assessmentsystem 905. As illustrated in FIG. 9, standalone sensor device 940 mayprovide the sensor data to a cloud server 945 for relaying to assessmentsystem 905. Cloud server 945 may include a data store 950 for storage ofsensor data received from standalone sensor device 940. It will beappreciated that data from sensors 931-939 may also be optionallytransmitted by client device 910 to cloud server 945 for optionalstorage by data store 950 and relay to assessment system 905. Sensordata collected by standalone sensor device 940 may, however, instead beprovided directly to assessment system 905 by a data push or a data pullcommunication.

Once data processor 920 possesses the sparse indicator data, the dataprocessor may analyze or characterize the sparse indicator information,such as by way of one more bucketing processes, such as depicted withrespect to FIG. 8. Possession of the sensor data from client device 910and/or standalone sensor device 940 may allow the data processor 920 tofurther characterize a state or status of the client associated with theclient device 910.

The analysis result(s) may be forwarded to a signal generator 955, whichmay use the analysis result(s), for example, to generate a communication960 indicating one or more likelihoods for the client to transition tothe particular state. In some embodiments, communication 960 may alsoidentify a change in likelihood, relevant sensor data and/or sparseindicator information that contributed to the likelihood analysis.

FIG. 10 shows a representation of a process 1000 for generatingcommunications using sparse indicator information and sensor data.Initially, at block 1005, a status analysis query may be received, suchas by an assessment system. Status analysis query may correspond to aninstruction from a client or requestor to perform a status analysis onbehalf of or corresponding to a client.

At block 1010, a client identifier may be determined. Optionally, theclient identifier may be directly obtained from the status analysisquery. Optionally, the client identifier may be obtained by performing alook-up in one or more data stores or databases. The client identifiermay be useful, for example, for later identifying other data, such assparse indicator information and/or sensor data associated with theclient.

Optionally, at block 1015, permission for accessing sparse indicatorinformation for the client may be obtained, such as by transmitting arequest for authorization and receiving authorization information. Forexample, the request may be generated by an assessment system andtransmitted to a client device or a requestor device for accesspermission. Upon receiving the request, the client device or requestordevice may obtain authorization, such as via one or more inputscorresponding to the authorization, for access by the assessment systemto the sparse indicator information.

At block 1020, a database or data store is queried to obtain sparseindicator information associated with the client. For example, theclient identifier determined at block 1010 may be used to facilitateobtaining the sparse indicator information, such as by including theclient identifier in the query. If required, authorization informationobtained at block 1015 may be included in the query to the database ordata store.

Optionally, an initial status analysis may be performed using the sparseindicator information, such as indicated in FIG. 10 at block 1025. Theinitial status analysis may correspond, for example, to an initialstatus analysis performed without use of sensor data.

The status analysis results so obtained may optionally be compared, atblock 1030, with one or more other client's status analysis results.Optionally, the one or more other client's status analysis resultscorrespond to an aggregated status analysis results. For example, anaverage, median, or mode likelihood of all clients having statusanalyses performed may be used as the aggregated status analysis result.As another example, the aggregated status analysis result may correspondto an average, median, or mode likelihood of clients sharing one or morecharacteristics with the client for which the present analysis is beingperformed.

At block 1035, a communication providing the initial status analysisresult and results of the comparison may optionally be generated. Atblock 1040, the communication providing the initial status analysisresult and results of the comparison may be transmitted. Optionally, theinitial status analysis result and results of the comparison may bestored without transmission at this point and retrieved at a later timepoint for transmission. For example, the initial status analysis resultand results of the comparison may be retrieved and added to a laterstatus analysis communication transmission.

At block 1050, sensor data may be obtained. Without limitation, thesensor data obtained may correspond to one or more of chemical sensordata, potentiometric sensor data, solute sensor data, microfluidicsensor data, environmental sensor data, activity sensor data,accelerometer data, altitude sensor data, biometric sensor data,location sensor data, weather sensor data, biometric sensor data,biomarker sensor data, pH sensor data, cytometric sensor data, opticalsensor data, smoke detector data, particulate sensor data, electricalcurrent sensor data, electrical resistance sensor data, and electricalimpedance sensor data. It will be appreciated that other sensor data notenumerated here may be obtained. The sensor data obtained may beassociated with the client. For example, the sensor data may be obtainedusing one or more sensors incorporated into a client device, such as awearable device, or using one or more sensors associated with a locationof the client. The sensor data may be obtained at block 1050 in responseto an optional transmission of a query, as indicated by block 1045, to aremote device for the sensor data. The sensor data may provide anindication of a current quality of the client. For example, the sensordata may provide information regarding one or more solutes used toidentify or indicate a state of the client. In some embodiments, thesolute may be present on a surface of the client or in a fluid obtainedfrom the client.

At block 1055, an (updated) status analysis is performed using thesparse indicator information obtained at block 1020 and the sensor dataobtained at block 1050. The (updated) status analysis may provideinformation relative to a likelihood of the client for transitioning toa particular state based on the sparse indicator information and thesensor data. Optionally, a comparison may be made between the results ofthe status analysis performed at block 1025 and the (updated) statusanalysis performed at block 1055. In this way, the impact of the sensordata on the status analysis can be directly determined via thecomparison.

At block 1060 a communication is generated providing, at least, theresults of the (updated) status analysis. If an initial status analysiswas performed at block 1025, the result of this initial status analysismay optionally be included in the communication. Optionally, sensor datamay also be included in the communication.

Optionally, at block 1065, a target status analysis may be generated,such as will be described below with reference to FIG. 11. Target statusanalysis may be generated using one or more of sparse indicatorinformation obtained at block 1020, sensor data obtained at block 1050,and analysis results generated at block 1055, and information related tothe target status analysis may be added to the communication generatedat block 1060. For example, the results of the target status analysismay be added to the communication. As another example, target sensordata that may be identified in a process of determining the targetstatus analysis may be added to the communication.

At block 1070, the communication may be transmitted. For example, thecommunication may be transmitted to a client device and/or to arequestor device. It will be appreciated that blocks 1050-1070 may berepeated one or more additional times, such as on a periodic oraperiodic basis, as updated sensor data is obtained.

Referring next to FIG. 11, a representation of a system 1100 foranalyzing sparse indicator information and sensor data is shown. System1100 may represent portions of assessment network 100 or 300 and may,for example, include additional or fewer elements than indicated in FIG.11. System 1100 may be in data communication with one or more othercomponents of assessment network 100 or 300 not shown in FIG. 11, suchas requestor device, one or more facilities, one or more datagenerators, and/or one or more data stores, for example.

System 1100 includes an assessment system 1105 and client device 1110.Client device may generate and transmit an analysis request 1115 toassessment system 1105 to initialize determination of a status analysisfor a client using sparse indicator information associated with theclient and sensor data associated with the client. Analysis request 1115may be received at a data processor 1120 of assessment system 1105, forexample. Data processor 1120 may query a data store to obtain the sparseindicator information 1125 associated with the client. The dataprocessor 1120 may use the sparse indicator information 1125 in theperformance of a status analysis to determine a likelihood for theclient of transitioning into a particular state.

Data processor may also query the data store to obtain aggregatedinformation 1130, which may be associated with or related to sparseindicator information for a plurality of other clients. For example,aggregated information 1130 may include sparse indicator information forthe plurality of other clients and then the sparse indicator informationfor the plurality of other clients may be used in analyses to determinelikelihoods for the plurality of other clients of transitioning into theparticular state. The determined likelihoods for the plurality of otherclients may then be aggregated (e.g., averaged) and used in a comparisonof the likelihood determination for the client of transitioning into theparticular state. As another example, aggregated information 1130 maycorrespond directly to the aggregated likelihood. In these ways, theclient may be able to see how they compare with another population. Inone embodiment, the plurality of other clients share one or morecharacteristic(s) with the client.

Assessment system 1105 may also receive sensor data from sensor 1135,which may be forwarded directly and/or automatically from sensor 1135 todata processor 1120 in a sensor data push configuration. Althoughillustrated in FIG. 11 as a separate sensor, sensor 1135 may optionallybe integrated into client device 1110, similar to sensors 930 depictedin FIG. 9.

It will be appreciated that, in some embodiments, client device 1110 mayinclude or have installed thereon software applications for interfacingwith sensor 1135 or otherwise facilitating the collection of sensor datafrom sensor 1135. In some embodiments, a first software application isinstalled on client device 1110 for generating analysis request 1115 anda second software application is installed on client device 1110 forobtaining sensor data from sensor 1135. Optionally, a third softwareapplication is installed on client device 1110 for forwarding offacilitating forwarding of sensor data from sensor 1135 to assessmentsystem 1105. Optionally, forwarding or facilitating forwarding of sensordata from sensor 1135 to assessment system 1105 includes forwardingsensor data from sensor 1135 to assessment system by way of one or moreintermediate networked systems, such as a cloud server.

Optionally, sensor data from sensor 1135 may be obtained by assessmentsystem 1105 in a data pull configuration. For example, data processor1120 may transmit a sensor data query to sensor 1135 or a systemassociated with sensor 1135, such as a cloud server that stores datagenerated by sensor 1135 or client device 1110, etc., and the sensordata may be transmitted to data processor 1120 in response to the sensordata request. A sensor data query may include information associatedwith the particular client, such as an identifier associated with theparticular client, in order to allow the appropriate sensor datagenerated by sensor 1135 to be returned to assessment system 1105, suchas in a configuration where a cloud server stores sensor data associatedwith a plurality of individuals. In some embodiments, permission orauthorization for access to sensor data may be requested and provided tosensor 1135 or a system associated with sensor 1135 to ensure securityand appropriate access to the sensor data.

Data from sensor 1135 may be used with sparse indicator information 1125by data processor 1120 in a status analysis to determine a likelihoodfor the client transitioning to a particular state. The analysisresult(s) and aggregated likelihood, for example, may be forwarded to asignal generator 1140, which may use the analysis result(s) andaggregated likelihood information to generate a communication 1145indicating one or more likelihoods for the particular client totransition to the particular state and comparing with aggregatedlikelihoods. Optionally, communication 1145 may include sensor dataobtained by sensor 1135.

FIG. 11 also depicts a target generator 1150, which may use sparseindicator information, sensor data from sensor 1135, and analysisresults from a status analysis in determination of one or more targets.Optionally, targets may include, for example, target likelihoods fortransitioning to a particular state. Optionally, targets may include,for example, target sensor data. Optionally, targets may facilitate theclient changing behavior or exposure to impact a likelihood oftransitioning to a particular state.

Target generator 1150 may optionally obtain sparse indicator informationand/or analysis results from data processor 1120. In addition, targetgenerator 1150 may obtain sensor data from sensor 1135 or a systemassociated therewith using a data push or data pull configuration.Optionally, sensor data may be provided to target generator 1140 by dataprocessor 1120.

Target generator 1150 may use all, none, or portions of the sparseindicator information 1125, sensor data from sensor 1135, and analysisresults generated by data processor 1120 in generating targets. Forexample, it may be desired to generate a target likelihood of a clienttransitioning to a particular state, and this target likelihood may beidentified, at least in part, by changing one or more parameters sensedby the sensor 1135. In this way, target generator may generate one ormore target likelihoods and obtain recommended changes (i.e., targetsensor data) for achieving the target likelihoods. As an example, airquality data may be obtained by sensor 1135, and target generator 1150may generate a target air quality metric in tandem with determination ofa target likelihood that is impacted by particular sensor data that maybe obtained by sensor 1135. Targets generated by target generator 1150may also correspond to actions or behaviors to be performed by a client.For example, different motion amounts of the client may correspond todifferent likelihoods of the client transitioning to a particular stateand so a target motion sensor value may be identified to facilitateachieving the target likelihood.

In a particular embodiment, the target(s) may be associated with actionsthat may affect a change in the likelihood of transitioning to aparticular state. In some embodiments, the targets may correspond to orbe associated with actions for increasing the likelihood oftransitioning to a particular state. In some embodiments, the targetsmay correspond to or be associated with actions for decreasing thelikelihood of transitioning to a particular state.

Optionally, sensor 1135 may be used to measure whether particulartargets are met or unmet by the client. For example, motion dataobtained by an accelerometer may be used by target generator 1140 inassessing whether a motion target for the client is met or unmet. Insome embodiments, information regarding whether a target is met or unmetmay be used in performing a further status analysis corresponding to adetermination of a likelihood of the client transitioning to aparticular state.

FIG. 12 shows a communication exchange between systems and devices of adata processing network, in accordance with some embodiments. Forexample, a client device 1205 may generate a status analysis query 1210that is received by an assessment system 1215. In order to perform therequested status analysis, assessment system may use sparse indicatorinformation. In some embodiments, the sparse indicator information isimmediately available at assessment system 1215. If the sparse indicatorinformation is not available, assessment system 1215 may generate andtransmit a sparse indicator query 1220 to a data store 1225 or a systemassociated with the data store. In response, the sparse indicatorinformation 1230 may be transmitted to assessment system. Optionally,assessment system 1215 may perform a status analysis 1235 using only thesparse indicator information 1230.

To perform a further status analysis, assessment system 1215 may usedata from sensor 1240. Sensor data 1245 from sensor 1240 may be providedto assessment system 1215 in a variety of ways. For example, sensor 1240may obtain and provide sensor data 1245 to client device 1205. Clientdevice may then push sensor data 1245 to assessment system 1215.Alternatively, assessment system 1215 may generate and transmit a sensordata pull query 1255 to client device and receive the pulled sensor data1260 in response. As another example, sensor 1240 may push sensor data1245 directly to assessment system 1215. Alternatively, assessmentsystem 1215 may generate and transmit a sensor data pull query 1255 tosensor 1240 and receive the pulled sensor data 1260 in response. Asanother example, sensor 1240 or client device 1205 may transmit sensordata 1245 to a cloud server 1265, such as by way of one or more datapush or data pull processes. Assessment system 1215 may receive sensordata 1245 pushed from cloud server 1265. Alternatively, assessmentsystem 1215 may generate and transmit a sensor data pull query 1255 tocloud server 1265 and receive the pulled sensor data 1260 in response.It will be appreciated that sensor data 1245 from sensor 1240 may alsobe obtained by assessment system 1215 by other techniques.

After obtaining sensor data 1245 from sensor 1240, assessment system mayperform a status analysis 1270 using the sparse indicator information1230 and the sensor data 1245. It will be appreciated from the foregoingdisclosure that the status analysis 1270 and status analysis 1235 mayinclude a likelihood of the client transitioning to a particular state.In addition, a comparison may be made between the results of statusanalysis 1270 and the status analysis 1235 to determine an impact of thesensor data 1245 on the likelihood of the client transitioning to aparticular state.

Target information 1275 may optionally be generated by target generator1280 and communicated to assessment system or a portion thereof for usein a target status analysis 1285.

Finally, a status analysis result(s) transmission 1290 may be generatedby assessment system 1215 and sent to client device 1205. It will beappreciated that the status analysis result(s) may correspond to resultsof status analysis 1235, status analysis 1270 and/or target statusanalysis 1285.

FIG. 13 shows a representation of a process 1300 for generatingcommunications including target information using sparse indicatorinformation and sensor data. Initially, at block 1305, a first statusanalysis is performed using sparse indicator information and sensordata, such as described above with reference to FIG. 9.

At block 1310, targets may be generated using one or more of the statusanalysis results, sparse indicator information, and sensor data, such asdescribed above with reference to FIGS. 10-12.

At block 1315, a first communication may be generated providing at leastthe status analysis results and the targets. Optionally, the firstcommunication may include information related to the sensor data and thesparse indicator data. The first communication may optionally provide acomparison of status analyses performed using only the sparse indicatorinformation, both the sparse indicator information and the sensor data,and of a target status analysis.

At block 1320, the communication may be transmitted. Depending on theentity requesting the status analysis and the particular status analysisrequest, the communication may be transmitted to one or more devices,such as a device associated with a requestor, a device associated with aclient, a device associated with a facility, etc.

Target(s) may be used by clients, for example, to facilitatemodification of behaviors or to facilitate performing actions that mayimpact a likelihood for transitioning to a particular state. Forexample, the target(s) may correspond to an instruction for a client tofollow. In order to determine whether the target(s) have been met orunmet by the client, sensor data related to the target(s) may be used.For example, sensors may be possessed by the client or located at a samelocation as the client or may monitor various characteristics of theclient and may aid in determining whether the target(s) have been met orunmet. For example, if a target corresponds to a particular action, asensor that monitors that particular action may provide informative dataregarding the target. As a specific example, if a target corresponds toan instruction for a client to reduce an exposure to particulates (e.g.,smoke), data from a particulate sensor monitoring an area occupied bythe client may provide insights as to whether the client is followingthe instruction.

At block 1325, additional sensor data is received, such as sensor datarelated to the targets or sensor data relating to or providing anindication of an updated state of the client. Optionally, the sensordata related to the targets may be directly received. Optionally, thesensor data related to the targets may be received in response to aquery for the sensor data, as described above. Optionally, the sensordata may be received directly from the sensor that generated the sensordata. Optionally, the sensor data may be received from a client deviceassociated with or including the sensor. Optionally, the sensor data maybe received from a cloud server.

At block 1330, an updated status analysis may be performed using one ormore of the sparse indicator information, the sensor data used in block1305, and the additional sensor data, such as sensor data related to thetargets or sensor data relating to an updated state of the clientreceived at block 1325. This status analysis may be compared with aprevious status analysis generated using the sparse indicatorinformation and previous sensor data. The status analysis may optionallybe compared with a previous target status analysis.

At block 1335, an updated communication may be generated providing atleast the updated status analysis results. Optionally, the updatedcommunication may include information related to the update sensor data,the sparse indicator information, and the sparse indicator data. Atblock 1320, the communication may be transmitted. Depending on theentity requesting the status analysis and the particular status analysisrequest, the communication may be transmitted to one or more devices,such as a device associated with a requestor, a device associated with aclient, a device associated with a facility, etc.

It will be appreciated that receiving updated sensor data related to thetargets may allow for tracking of whether the targets have been met orunmet. Further, receiving the updated sensor data may also allow forreevaluation of the likelihood of the client transitioning to aparticular state based on the updated sensor data. This reevaluation mayfacilitate the client determining whether progress towards the target isbeing achieved and/or whether the target is further away in view of theupdated sensor data.

Referring next to FIG. 14, a genetic assessment network 1400 is shown inone embodiment. Through the interaction of multiple devices andentities, an assessment system 1405 can generate an output that includesa risk variable and/or risk assessment indicating an estimated risk ofeach of one or more particular conditions (e.g., breast cancer andovarian cancer) for a particular individual (also referred to herein asa client or subject).

More specifically, assessment system 1405 receives an electronic requestfrom a requestor device 1410. Assessment system 1405 may include one ormore electronic devices (e.g., servers and/or computers) and may, butnot need, reside partly or entirely at a remote server. Requestor device1410 may be one configured and located to receive input from a physician1415. In one instance, requestor device 1410 a is located in an externalphysician-associated facility 1420, such as a physician's office orhospital. In one instance, requestor device 1410 b includes aninternally linked requestor device 1410 b, such as ones that itselfreceive invitations, from assessment system 1405, to generate electronicrequests.

The electronic request can include an order to conduct a geneticanalysis and/or to conduct one or more types of risk assessments. Theelectronic request may identify, or otherwise indicate, one or moreconditions to be evaluated during the genetic analysis and/or riskassessment. The electronic request may identify a patient and/or includeadditional data pertaining to the patient, such as identifying, health,and/or medication data of the patient.

The patient may be equated to, by assessment system 1405, a client 1425.In some instances, a client device—associated with client 1425—initiallytransmits a preliminary electronic request for the genetic analysisand/or risk assessment to assessment system 1405. For example, such apreliminary electronic request may be initiated via client interactionwith a website associated with assessment system 1405. The same or asubsequent preliminary request may identify a particular physician(e.g., by name, office location, phone number, and/or email address)and/or may request that a physician 1415 b associated with an internallylinked requestor device 1410 b submit such a request.

When a particular physician (or other medical entity) is identified in apreliminary electronic request, assessment system 1405 may identify adestination address (e.g., IP address or email address) associated withthe physician and transmit a communication identifying informationassociated with the preliminary request (e.g., the client, a type ofgenetic analysis, and so on). The communication may include a partialorder and/or an input field that would confirm that the order requestedby client 1425 is to be generated and transmitted back to assessmentsystem 1405. Such a communication may facilitate receipt of theelectronic request from requestor device 1410 b.

When it is requested that a physician 1410 b associated with aninternally linked requestor device 1410 b submit such a request,assessment system 1405 may transmit a similar communication to arequestor device 1410 b that may have been selected from amongstmultiple internally linked requestor devices. The selection may be basedon a load balancing technique, physician office hours, physicianexpertise, locations of the multiple requestor devices, a pseudo-randomselection technique, and/or an insurance affiliation.

Once the electronic request has been received from a requestor device1410 (e.g., in response to a preliminary electronic request from aclient device 1430), assessment system 1405 may evaluate the electronicrequest to ensure that all required data (e.g., which may include aname, address, insurance, billing and/or payment information, such ascredit card information) has been provided from physician 1415 a andthat all required data pertaining to client 1425 has been identified(e.g., via the electronic request, a preliminary request and/or storeddata). If assessment system 1405 determines that all requiredinformation has not been identified, a request for such information maybe transmitted to requestor device 1410 and/or client device 1430.

When all required information has been provided, assessment system 1405can send an instruction communication to a distribution device 1435. Theinstruction communication can include (for example) a name and addressof client 1425 and, in some instances, an indication as to what is to besent to client 1425. For example, an electronic request may indicate atype of analysis that is to be performed on a biological sample (e.g., agenetic analysis pertaining to a risk of getting one or more particulartypes of cancers) and/or a type of biological sample (e.g., a salivasample) that is to be analyzed. The instruction communication mayidentify the type of analysis, type of biological sample and/or kitassociated with collection thereof. The instruction communication maythus facilitate and/or trigger a physical distribution of a kit forcollecting a biological sample to a client address. The kit may include,for example, instructions as to how to collect a sample, a container forstoring the sample, an envelope or package for sending the container andsample to be analyzed, and/or information pertaining to an order or typeof analysis to be conducted.

A sample from client 1425 may then be received at a laboratory 1440.Laboratory 1440 may include one or more assessment devices 1445configured to sequence all or part of the genome and/or all or part ofthe epigenome using the sample. For example, an assessment device 1445may include a DNA sequencer and/or PCR machine. Laboratory 1440 mayfurther include one or more technician devices 1450, such as a desktopor laptop computer. Data generated by or at one or more laboratorydevices (e.g., assessment device 1445 or technician device 1450) may bestored at a laboratory data store 1455, which may be remote from alllaboratory devices or part of a laboratory device. The laboratory datamay, for example, include identifying client information (e.g., a nameand address), laboratory information (e.g., location and name), devicespecifications (e.g., manufacturer and model of assessment devise) andgenetic data (e.g., genetic sequences).

An access control device 1460 a may control which devices and/orentities may gain access to the laboratory data, which may apply todevices and/or entities internal to laboratory 1440 and/or to devicesand/or entities external to laboratory 1440. Access control device 1460a may implement one or more rules, such as restricting access to clientdata to one or more particular devices (e.g., associated with assessmentsystem 1405). Such access may further or alternatively be controlled vialogins, passwords, device identifier verification, etc.

In various instances, access control device 1460 a controls access viacontrol of pushed transmissions and/or via control of processing pullrequests. For example, a rule may indicate that laboratory datapertaining to a sample is to automatically be transmitted to aparticular assessment system 1405 (and/or device associated therewith)upon completion of a laboratory-based assessment or detection ofparticular data (e.g., data matching a request). Access control device1460 a may then monitor for such a condition to be met and may thengenerate and transmit appropriate data.

In addition to receiving laboratory data, assessment system 1405 mayfurther collect one or more other types of data that may be used toassess, for example, a health risk. For example, one other type of datamay include health-related inputs provided at a client device 1430, suchas inputs that indicate medical history, current conditions, familialhealth statuses or conditions, age, eating habits, exercise patterns,occupation, exposure to environments associated with toxic chemicals,and so on. Another type of data may include data automatically detectedat a client device 1430. For example, a wearable client device may trackactivity patterns so as to estimate calories burned per day, or thewearable client device may estimate a pulse distribution, usertemperature, sleep patterns and/or indoor/outdoor time. This data may bedirectly transmitted (e.g., after a request and/or authorizationhandshake) to assessment system 1405 and/or via another client device(e.g., via accessing health data on a phone or computer client device).Yet another type of data may include protected health information (PHI)data and/or electronic medical record (EMR) data, which may be stored,for example, at a EMR data store 1465 at and/or associated with anexternal physician-associated facility, such as one having provided anelectronic request to perform an analysis or assessment pertaining to aclient and/or one as identified via input at a client device 1430. Toillustrate, the other data may identify one or more symptoms and/orphysician evaluation results for a client or may include a result of oneor more medical tests (e.g., mammogram, MRI, pulmonary function, EKG,etc.).

In various instances, the other data may be transmitted to assessmentsystem 1405 prior to any, or in response to a, request from assessmentsystem 1405 for such. For example, client input other data may beprovided as part of a preliminary request from client device 1430 andEMR data may be provided as part of an electronic request from requestordevice 1410 a. As another example, upon receiving a preliminary requestfrom a client device, assessment system 1405 may request that a clientauthorize access to health data stored on the client device, such thatit may be (e.g., via an app) retrieved and transmitted to assessmentsystem 1405.

Thus, assessment system 1405 may have access to—for a given subject—oneor more genetic sequences, epigenetic modification data, client-reporteddata, medical record data, medical test data, activity (e.g., exercise)data, and/or other types of data. Assessment system 1405 may thereforeevaluate genetic data in combination with other types of data in orderto generate a risk analysis result. In one instance, an initialevaluation involves detecting whether, for each data type, the dataincludes an abnormal data element (e.g., as evaluated with respect tothe human species or a particular population). For example, assessmentsystem 1405 may identify whether genetic data includes any variants withrespect to genes of interest, or assessment system 1405 further evaluatea medical history (e.g., as provided by a physician) to determinewhether the client had a prior cancer diagnosis. As another example, afamily history may be evaluated to determine whether an above thresholdnumber of relatives were diagnosed with cancer or whether a closerelative was diagnosed with cancer prior to a threshold age. As yetanother example, data from a wearable device may be assessed todetermine whether a client is not meeting a threshold for exerciseand/or for sleep or to determine whether a client is outside more than athreshold percentage of time.

Each one of these abnormalities may be individually associated with someincreased risk for being diagnosed with a condition, such as cancer.These associations may be identified via a local or remote look-uptable. Assessment system 1405 may aggregate the data in any of a varietyof manners. For example, assessment system 1405 may identify a maximum(quantitative or categorical) risk variable associated with each of two,more or all data types, or aggregate system 1405 may generate a weightedsum of risk variable. As another example, a protocol for how to generatean overall risk variable based on a combination of abnormality databased on a machine-learning or cluster protocol.

In some instances, a risk associated with a particular abnormality(e.g., variant) and/or with a combination of abnormalities is unknown oris associated with a below-threshold confidence. Upon detecting such anabnormality or combination (or a threshold quantity thereof), theparticular abnormality and/or combination can be identified in areview-request communication and sent to a reviewer device 1470.Reviewer device 1470 may then present the identification to a reviewer1475 and detect input that is indicative of an estimated risk toassociate with the abnormality and/or combination.

A result generated by assessment system 1405 can include a quantitativeor qualitative (e.g., categorical) risk variable. For example, the riskvariable may include a percentage probability or range of getting aparticular condition. As another example, the risk variable may includethree risk categories (low risk, moderate risk, and high risk).

Assessment system 1405 may generate an electronic report that includesthe result and/or that is selected based on the result. For example,different preventative-measure content may be included in reportsdepending on a risk category. As another example, a report may identifyone or more abnormalities (e.g., one or more variants) and/orcorresponding normal bases, ranges, data and so on. A report mayidentify a condition (e.g., disease) pertaining to an analysis (e.g.,“Breast Cancer Risk Analysis”). A report may identify types of data(e.g., particular genes and/or other type of data) used in the analysis.A report may identify a confidence in a result (e.g., a risk variable).A report may identify a recommendation (e.g., to consult with aphysician or to receive a particular medical test).

Assessment system 1405 may update and may have access to a variety ofdata stores, part or all of which may be remote from, co-localized withassessment system 1405, and/or included in assessment system 1405. Oneor more of the data stores may include a relational data store, suchthat data from one data store or structure within a data store may beused to retrieve corresponding data from another data store orstructure. The data stores may include, for example, an account datastore 1476, which may include login credentials for one or more usersand/or types of data access to be granted to each user; process datastore 1477, which may identify laboratory analysis characteristicspertaining to particular data elements (e.g., identifying a laboratory,piece of equipment and/or processing time); genetic data 1478, which mayidentify one or more genetic sequences associated with a given sample orclient; and/or epigenetic data store 1479, which may identify one ormore epigenetic sequences or signatures associated with a given sampleor client. The data stores may further or alternatively include aresults data store 1481, which may identify one or more abnormalitiesidentified by and/or one or more results generated by assessment system1405 that are associated with a given sample or client; a reports datastore 1482, which may include one or more report templates (e.g., eachassociated with one or more result types) and/or one or more reports tobe transmitted or having been transmitted to a client device; and/or arelevance support data store 1483, which may identify which types ofdata (e.g., genes, genome portions, activity patterns, inputs, medicalrecords, medical tests, etc.) are established to be, potentially,established not to be, or unknown whether to be relevant for evaluatinga particular type of risk (e.g., a risk of developing a particularcondition).

Genetic assessment network 1400 can also include a user device 1480configured to detect input from a user 185. User 185 may be associatedwith an account or other authentication data indicating that access tosome or all of the data is to be granted. Accordingly, user 185 may beable to interact with various interfaces (presented at user device 1480)to view data pertaining to one or more particular clients (e.g., in anidentified or deidentified manner), to view summary data that relates todata from multiple clients, to explore relationships between data types,and so on. In some instances, an interface may be configured to acceptinputs from a user 185 so as to enable the user to request datapertaining to samples with variants in particular genes; particularvariants; particular phenotypes or condition risks; ethnicityinformation; trait information; symptom presence; and/or family-historypatterns.

Genetic assessment network 1400 can also include an external assessmentdevice 1490 configured to detect input from a developer 1495. Via suchinputs, external assessment device 1490 may send electronic requests forgenetic and/or other data (e.g., relating to particular genes, aparticular client and/or particular client inputs) to assessment system1405. An electronic request from an external assessment device 1490 mayidentify, for example, particular portions of the genome and/orepigenome (e.g., requesting sequences of particular genes and/oridentification of any variants or epigenetic modifications detected atthe particular genes), family-history data pertaining to one or moreidentified conditions (e.g., any cancer), and/or medical record dataidentifying past diagnoses.

In some instances, an interface is configured to identify data typesthat may be or that are available for at least some subjects or for aparticular subject. For example, assessment system 1405 may provide awebpage that accepts queries for genes and ultimately allows a developer1495 to select particular genes of interest and what data pertaining tothe gene is of interest (e.g., a sequence, variant data, epigeneticmodification data, and/or categorizations of any variant or epigeneticmodification). Similarly, the interface may identify other types ofmedical-test data, medical-record data, subject input, activity-trackingdata, and so on that may be available, such that a developer 1495 mayselect data of interest. These fields may identify, for example, typesof data available for a particular subject (e.g., one having beenidentified via input from the developer), types of data that thedeveloper is authorized (e.g., generally or upon receiving clientapproval) to access, or types of data collected for at least one subjectin a set of subjects. Thus, one or more interfaces may enable adeveloper 1495 to specify a semi-arbitrary collection of data ofinterest.

Assessment system 1405 may evaluate the request to determine, forexample, whether a corresponding client 1425 authorized such access(which may be verified via a communication exchange between assessmentsystem 1405 and client device 1430) and/or whether such access isrelevant to a purported type of analysis. If the evaluation indicatesthat access is to be granted, assessment system 1405 may (for example)send an instruction communication to laboratory 1440 to conduct a newanalysis of an existing sample, send a data request to a device (e.g.,access control device 1460 b, client device 1430) and/or retrieve datafrom a data store (e.g., and extract pertinent information from anylarger data structure, such as extracting gene-specific data from agenome). Provision of such data may be conditioned upon or may requirepayment (e.g., by a client or developer) of a fee.

Various devices in genetic assessment network 1400 may communicate withone or more other devices in genetic assessment network 1400 via anetwork, such as the Internet, a local-area network or a short-rangenetwork. Communications may be sent in a secure manner to, e.g., inhibitunauthorized access to health data. Techniques such as tokenauthentication and/or encryption may be used.

It will be appreciated that the representations of devices andconfigurations depicted in FIG. 14 are illustrative. For example, whilea single laboratory 1440, client device 1430, and genetic data store1478, etc. are shown, a system may include multiple laboratories 1440,client devices 1430, genet data stores 1478, etc. As another example,while access control devices 1460 a, 1460 b are shown as being connectedto laboratory data store 1455 and EMR data store 1465, additional accesscontrol devices may be present in system 1400. For example, an accesscontrol device 1405 may be included within or connected to assessmentsystem 1405 so as to control access that requestor device 1410 b, clientdevice 1430, distribution device 1435, reviewer device 1470, user device1480 and/or external assessment device 1490 may achieve.

Referring next to FIG. 15, an embodiment of a process 1500 forconducting risk analyses based on genetic information is shown. Process1500 may be performed in part or in its entirety by, for example,assessment system 1405. At block 1505, an electronic request is receivedfrom a first device for a biological analysis for a client. In oneinstance, the electronic request includes a preliminary request from adevice associated with the client. The preliminary request may have beenreceived via a website and may identify and/or be associated with acondition for which a risk is to be assessed (e.g., a cancer type). Forexample, the request may include a submission of input on a webpageidentifying a type of risk analysis for breast cancer, where the inputidentifies the client.

In one instance, the electronic request includes, for example, a request(e.g., order) from a device associated with an external or internallylinked physician. The electronic request can identify the client (e.g.,by name and/or address). The electronic request can identify a condition(e.g., disease) that the biological analysis is to pertain to. Forexample, the electronic request can indicate that Physician X isordering a lab-based assessment to be conducted that for Patient Y todetermine how much at risk Patient Y is for developing Cancer Z.

At block 1510, genetic information associated with the client isaccessed. In one instance, the genetic information is retrieved from alocal or remote data store using an identifier of the client. Thegenetic information may include data provided from a lab device or dataprovided by an external system controlling the data. The geneticinformation may identify one or more sequences (e.g., pertaining to eachof one or more genes). The genetic information may identify whether oneor more variants were detected and/or what variants were detected.

At block 1515, a second electronic device associated with the client isidentified. In instances where the request received at block 1505 wasfrom a first device associated with the client, the second electronicdevice may (but need not) be a different device than the first device.The second electronic device may include, for example, a wearabledevice, a smart phone or a computer. The electronic device can include,for example, a device that has access to health, activity, or exercisedata. In one instance, the second electronic device (or yet anotherdevice associated with the client) includes one or more sensors thatcollect data related to the health, activity or exercise data. Forexample, the sensors may include an accelerometer and/or gyroscopeand/or may be configured to detect movement, location, heart rate and soon. Such sensor data may be processed to estimate, for example, apercentage of the day that the client was exercising, sleeping, sitting,etc.; number of calories burned; and/or heart-rate distributioncharacteristics. Such statistics may be stored locally at thesensor-including device and/or transmitted to another electronic deviceassociated with the client, such that the statistics may be provided byeach of one or both of the devices.

At block 1520, an electronic request for data that includes anindication of an activity or status of the client is transmitted to thesecond device. For example, the request may be for data including anindication of activity, such as data indicating how many steps a clienttakes on an average day, a median estimated calorie burn per day, or amean and standard deviation of nightly sleep hours. As another example,the request may be for data including an indication of status, such as aheart rate status. The data is received from the second device inresponse to the request at block 1525.

At block 1530, a risk analysis is generated based on the geneticinformation and data. The risk analysis may be further based on othertypes of data as well, such as medical record data, medical test data,and/or client inputs. The risk analysis may include a risk variable,such as a risk category.

The risk analysis (e.g., a risk variable) is transmitted to the firstdevice. The risk analysis may be transmitted, for example, as part of anelectronic report. The transmission may include sending the riskanalysis to an email address or account identifier of the client, suchthat the risk analysis may be retrieved by the client upon accessing theaccount or email account.

Process 1500 may, in some instances, return to repeat one or moreblocks. Upon such a return, the process may thereafter proceed torepeated each of one or more of the blocks subsequent to the returnblock. For example, it may be determined that additional geneticinformation is pertinent to the biological analysis, such that block1510 is repeated to access the additional genetic data such that it canbe evaluated during a repeated generation of the risk analysis. Asanother example, a new (additional or subsequent) second deviceassociated with the client may be identified (e.g., via provision ofclient input at a webpage or on a known client device identifying thenew device or automated short-range detection of a particular devicetype, such as a wearable device, at a known client device). Blocks 1515,1520, 1525 and 1530 may then be repeated to utilize new activity- and/orstatus-related data made available via the new device. As yet anotherexample, a known second device may provide new data (e.g., thatidentifies updated or changed activity patterns or recent sleepschedules) via a repetition of block 1525, which may be used to updatethe risk analysis at block 1530. As still another example, block 1530may be repeated to generate a risk analysis using existing data but in adifferent manner (e.g., by applying different weights to data orcombining it with additional types of data). In each of these instances,transmission of an updated risk analysis may be performed via arepetition of block 1535 upon, for example, mere generation of theupdated risk analysis, detecting a change in the risk analysis (or atleast a threshold change), detecting that a defined time period haselapsed since a prior transmission, and so on.

Referring next to FIG. 16, an embodiment of a process 1600 forconducting risk analyses based on genetic information is shown. Process1600 may be performed in part or in its entirety by, for example,assessment system 1405. At block 1605, an electronic request is receivedfor a biological analysis for a client. In one instance, the electronicrequest includes a preliminary request from a device associated with theclient. The preliminary request may have been received via a website andmay identify and/or be associated with a condition for which a risk isto be assessed (e.g., a cancer type). For example, the request mayinclude a submission of input on a webpage identifying a type of riskanalysis for breast cancer, where the input identifies the client.

In one instance, the request may be received from a device associatedwith an external or internally linked physician. The electronic requestcan identify the client (e.g., by name and/or address). The electronicrequest can identify a condition (e.g., disease) that the biologicalanalysis is to pertain to. For example, the electronic request canindicate that Physician X is ordering a lab-based assessment to beconducted that for Patient Y to determine how much at risk Patient Y isfor developing Cancer Z.

At block 1610, one or more portions of the human genome pertinent to theanalysis are identified (e.g., via a look-up table or rule). The one ormore portions may include, for example, one or more genes.

At block 1615, a first presentation is generated that identifies the oneor more portions (e.g., by gene name) and that identifies support forcontending that the one or more portions are pertinent for conductingthe biological analysis. The support may include, for example, citationsof and/or links to articles, summaries of published or unpublished dataand/or reference to one or more other entities or data stores thatassociate a given portion with a condition associated with the analysis.

The first presentation further indicates that one or more other portionsmay later be identified as being relevant to the analysis (e.g., by anentity requested to conduct the analysis and/or other entity). The firstpresentation further includes one or more input fields. The one or moreinput fields may include, for example, an accept button thatacknowledges terms of conducting an analysis and/or accessing data. Invarious instances, a single input (e.g., of an accept option) may beindicative of an authorization to conduct an original analysispertaining to a risk analysis for a condition and to conduct a post-hocanalysis should one or more other portions subsequently be identified aspertaining to a risk analysis for a condition, or one input mayauthorize an original analysis and another may indicate whether apost-hoc analysis is authorized as well.

The first presentation may be transmitted to a device having transmittedthe request received at block 1605 and/or a device of the client. Thefirst presentation may be presented, for example, via a webpage.

At block 1620, a communication is received that indicates that one ormore inputs were detected. The one or more inputs may authorize theoriginal analysis and may indicate whether (or that) a post-hoc analysisis authorized.

At block 1625, data indicating that the client authorized an originalanalysis (e.g., and, in some instances, identifying a type of analysisis stored). For example, data may be stored that includes identifyinginformation about the client and the date that the input-indicatingcommunication was received. In one instance, the one or more inputfields in the first presentation are configured such that anauthorization is either provided for both the original and for post-hocanalyses or for neither. In such instances, separate indications as towhether a post-hoc analysis was authorized may not be needed. In oneinstance, the one or more input fields are configured to enable anauthorization for an original analysis to be provided and either anauthorization or rejection (e.g., via an opt-in or opt-out input) ofpost-hoc analysis to be provided. The stored data may then reflectwhether such post-hoc analysis was authorized.

At block 1630, a second presentation is generated that identifies one ormore results of the original analysis identified based on geneticinformation associated with the portion(s) of the genome. The secondpresentation may be transmitted to a device having transmitted therequest received at block 1605 and/or a device associated with theclient. The second presentation may be presented, for example, via awebpage or an email.

At block 1635, one or more additional portions of the genome (e.g., oneor more additional genes) are identified as being pertinent to theanalysis. Such identification may be a result, for example, of detectingan update in a look-up table or rule.

At block 1640, it is determined whether authorization was provided toperform post-hoc analysis for the client. Such determination may be madeby using the data stored at block 1625 (e.g., querying a data storeusing an identifier of the client). When it is determined that post-hocanalysis was authorized, the additional portion(s) of the client'sgenome may be accessed, which may involve (for example) retrieving thedata from a local data store or a remote data store controlled byassessment system 1405; sending an electronic request with an identifierof the one or more additional portions and the client to another device;and/or facilitating performing a new laboratory analysis on a storedbiological sample of the client. The additional portion(s) of theclient's genome may then be used to generate one or more results, whichmay include (for example) an updated risk variable and/or whether(and/or how) a risk variable changed since a previous (e.g., original)analysis. A third presentation is then generated at block 1645 thatidentifies the one or more results. The third presentation may include areport, may identify the one or more additional portions and/or mayidentify support for a contention that each of the one or moreadditional portions pertains to the biological analysis (e.g., viaidentification of one or more articles). The third presentation may betransmitted to a device having transmitted the request received at block1605 and/or a device of the client and may be presented at the devicevia a webpage or email.

When it is determined that post-hoc analysis was not authorized, afourth presentation is generated at block 1650 that identifies the oneor more additional portions and support for a contention that each ofthe one or more additional portions pertains to the analysis (e.g., byidentifying and/or linking to articles). The fourth presentation furtherincludes an input field that may be configured to receive an inputindicating that performance of the post-hoc analysis (and/or access tothe one or more additional portions) is authorized. The fourthpresentation may be transmitted to a device having transmitted therequest received at block 1605 and/or a device of the client and may bepresented at the device via a webpage or email.

It will be appreciated that, in some instances, a post-hoc analysis neednot use an additional portion of the genome. For example, newunderstandings may indicate how various aspects of a given gene shouldbe processed differently to evaluate a risk of a condition. As anotherexample, a post-hoc analysis may relate to a new condition (e.g., apreviously detected variant discovered while investigating a risk fordeveloping a first condition (e.g., cancer) may be uncovered to beinformative as to a risk for developing a second condition (e.g.,dementia)). As yet another example, a post-hoc analysis may relate to apredicted efficacy of one or more treatments in treating a condition.

Referring next to FIG. 17, an embodiment of a process 1700 forconducting risk analyses based on genetic information is shown. Process1700 may be performed in part or in its entirety by, for example,assessment system 1405. At block 1705, one or more first portions of thegenome (e.g., one or more genes) to be used to generate a risk variable(e.g., identifying a predicted likelihood of developing a medicalcondition or disease) are identified. The one or more first portions maybe identified, for example, based on a look-up table or rule.

At block 1710, for a given client, a first risk variable is generatedbased on first genetic data corresponding to the first portion(s). Theclient can include one for which a request for conducting the analysiswas received and/or for which lab data has been availed (e.g., receivedfrom a lab device). At block 1715, a first electronic report thatincludes the first risk variable is generated and transmitted to adevice of the client. Blocks 1710 and 1715 can be repeated for one ormore other clients.

At block 1720, it is determined whether one or more second portions havebeen identified as ones to be used to generate the risk variable. Forexample, an update in a look-up table or rule may indicate that they areto be used. When it is determined that the one or more second portionsare to be used, process 1700 continues to block 1725 where a set ofclients are identified. The set of clients can include, for example, aset in which a biological analysis of a particular type (e.g.,pertaining to a particular condition or disease) had been conducted foreach client in the set and/or each client in the set provided inputindicative of an authorization of a post-hoc analysis. Each of blocks1730-1740 is then performed for each client in the set.

At block 1730, a second risk variable is generated based on secondgenetic data corresponding to the second portion(s). The second riskvariable may also be based on each of one, more or all of the one ormore first portions. At block 1735, it is determined, based on thesecond risk variable, whether a follow-up transmission condition issatisfied. For example, a follow-up transmission condition may beconfigured to be satisfied when, for a given client, a second riskvariable is different than a first risk variable or is different by atleast a threshold amount or in a threshold manner (e.g., such that thesecond risk variable indicates more risk than did the first riskvariable).

When it is determined that the follow-up transmission condition issatisfied, at block 1740, a second electronic report is generated toinclude the second risk variable and transmitted to a device of theclient. The second electronic report may indicate that the risk variablehad be regenerated and/or identify the first risk variable.

FIG. 18 shows an embodiment of a process 1800 for evaluatinggenetic-data queries based relevance assessments. Process 1800 may beperformed in part or in its entirety by, for example, assessment system1405. At block 1805, a query is received (via an electroniccommunication) that includes a specification of a type of genetic data.The specification may include an identification, for example, of one ormore portions of the genome (e.g., one or more genes). In someinstances, the query further identifies a subject (e.g., person) and/ora set of subjects. The query may be received, for example, from adeveloper device or device with account data indicating that access togenetic data is restricted.

At block 1810, an indication of a type of analysis to be conducted usingthe genetic data is received. The indication may include, for example,an identification of one or more types of diseases (e.g., one or moretypes of cancer). Thus, in one instance, blocks 1805 and 1810 includereceiving one or more communications that request genetic data (e.g.,identifying sequences and/or variants) pertaining to one or more genesfor each of one or more subjects such that an analysis can be conductedpertaining to a risk of those subject(s) for developing a particulardisease.

At block 1815, a local or remote data store is queried using thespecification (e.g., and an identifier of each of the one or moreclients).

At block 1820, a determination is made as to whether there is asufficient indication that the type of genetic data requested via thequery is relevant to the analysis identified at block 1810. For example,block 1820 may include determining whether evaluating data pertaining toeach of a set of identified genes is informative with regard to a riskof developing a particular cancer. This determination may be made, forexample, using a data structure that associates particular genes andconditions and/or via execution of a defined rule.

When it is determined that sufficient indication is available, process1800 continues to block 1825, where it is verified that access to dataretrieved at block 1815 is authorized. When such a verification is made,the data is transmitted at block 1830.

When it is determined that sufficient indication is not available,process 1800 continues to block 1835, where one or more responsecommunications are generated. The one or more response communicationscan identify that it was determined (as block 1820) that there was not asufficient indication that the type of genetic data requested via thequery is relevant to the identified analysis. The one or more responsecommunications can further indicate that a renewed request for thegenetic data would be strengthened by provision of additionalinformation supporting the relevance. The additional information mayinclude, for example, identification of one or more articles or studiesand/or provision of unpublished data. The one or more responsecommunications may identify how such additional information may beprovided. In one instance, such additional information may be identifiedeven without explicit identification or provision of such from an entityassociated with the query. For example, a look-up table and/or rule maybe updated in time based on new articles or studies. At block 1805, theresponse communication is transmitted to a device having transmitted thequery,

FIG. 19 shows an embodiment of a process 1900 for differentiallyresponding to requests for access to genetic data based onsubject-provided permission types. Process 1900 may be performed in partor in its entirety by, for example, assessment system 1405. At block1905, a request for genetic data corresponding to a subject is received.The request may be received, for example, from a developer device. Therequest may (in some instances) correspond to or indicate that a wholegenome is requested or that one or more particular portions are beingrequested. The request may identify the subject, for example, by nameand/or other identifier (e.g., social security number).

At block 1910, the genetic data corresponding to the data is retrievedfrom a local or remote data store. The genetic data may include, forexample, one or more sequences and/or identification of variants.

At block 1915, a determination is made as to what type of permissiontype was granted by the subject with regard to data access. Thedetermination may be made, for example, by querying a data store (e.g.,a permissions or account data store) or by transmitting a communicationto a device of the client to request identification of the permissiontype (e.g., the communication identifying an entity requesting access)and receiving a corresponding respond.

A first permission type may result in process 1900 proceeding to block1920, where other data corresponding to the subject is retrieved. Theother data may include, for example, responses provided via input to oneor more questions via a webpage, medical record data, data from or basedon a client device's sensor data indicative of a subject's activity orstatus, etc. At block 1925, a first response type may be generated thatfacilitates access to the subject's genetic data and to the other data.For example, a response may include the data or may provide one or moreelectronic addresses at which some or all of the data can be found.

A second permission type may result in process 1900 proceeding to block1930, where a second response type is generated that facilitates accessto the genetic data. However, the second response type may notfacilitate access to the other data (or at least to all of the otherdata) for which access is facilitated in response to detecting the firstpermission type.

A third permission type may result in process 1900 proceeding to block1935, where a third response type is generated that indicates thataccess to the genetic data is denied.

FIG. 20 shows an embodiment of a process 2000 for processing customqueries from external assessment devices for genetic and/or epigeneticdata. Process 2000 may be performed in part or in its entirety by, forexample, assessment system 1405. At block 2005, one or more electronicrequest communications are received from an external assessment device.The one or more request communications can identify a client (e.g., byname, social security number or other identifier) and/or one or moregenes (e.g., by name; by specifying a chromosome, chromosome arm, andposition on the arm; or molecular address). The external assessmentdevice can include a device associated with (e.g., owned and/or operatedby) a developer. The client and/or gene(s) identified in the requestcommunication(s) may correspond to a client and/or gene(s) identifiedvia input from a developer provided at the external assessment device.

At block 2010, one or more types of genetic and/or epigenetic data beingrequested is determined. The one or more types may be, for example,identified within the request communication(s) (e.g., reflective ofdeveloper input), identified via a preference or authorization for adeveloper, etc. The type of genetic and/or epigenetic data can include,for example, a genetic sequence, an epigenetic sequence, whether (e.g.,and where and of what type) a genetic variation was detected, whether(e.g., and where and of what type) an epigenetic modification wasdetected, a categorization (e.g., pathogenic or benign) of any detectedgenetic variation, and/or a categorization of any detected epigeneticmodification.

At block 2015, it is determined whether data of the requested type forthe requested gene(s) and client is or can be available. For example,the determination may involve determining whether the gene(s) had beensequenced for the client, whether a sample remains available foradditional sequencing and/or whether processing of existing sequences ispossible (e.g., to identify variants).

When it is determined that the data is (e.g., and, in some instances,cannot be) available, process 2000 continues to block 2020 where aresponse communication denying the request is generated and transmittedto the external assessment device. When it is determined that the datais (e.g., or can be) available, process 2000 continues to block 2025where it is determined whether a developer associated with the externalassessment device is authorized to access the data. The determinationmay be made, for example, by looking up authorizations associated withthe developer and client or by transmitting a communication to a deviceof the client (e.g., identifying the developer and gene(s)) requestingwhether access is authorized and monitoring for a reply.

When it is determined that the developer is not authorized to accessdata, process 2000 again continues to block 2020 where a responsecommunication denying the request is generated and transmitted to theexternal assessment device. When it is determined that the developer isauthorized to access the data, process 2000 continues to block 2030,where the data is retrieved from a remote or local data store (e.g., bysubmitting a query that includes an identifier of the client and of thegene(s)).

At block 2035, any processing on the data is performed. For example,processing may include filtering the data to remove information (e.g.,client-identifying information). As another example, processing mayinclude transforming the data to be of the requested type of geneticand/or epigenetic data. At block 2040, the retrieved data (or processedversion thereof) is transmitted to the external assessment device. Forexample, the data may be transmitted over a webpage and/or madeavailable via a download.

Substantial variations may be made in accordance with specificrequirements. For example, customized hardware might also be used,and/or particular elements might be implemented in hardware, software(including portable software, such as applets, etc.), or both. Further,connection to other access or computing devices such as networkinput/output devices may be employed.

In the foregoing specification, aspects of the invention are describedwith reference to specific embodiments thereof, but those skilled in theart will recognize that the invention is not limited thereto. Variousfeatures and aspects of the above-described invention may be usedindividually or jointly. Further, embodiments can be utilized in anynumber of environments and applications beyond those described hereinwithout departing from the broader spirit and scope of thespecification. The specification and drawings are, accordingly, to beregarded as illustrative rather than restrictive.

In the foregoing description, for the purposes of illustration, methodswere described in a particular order. It should be appreciated that inalternate embodiments, the methods may be performed in a different orderthan that described. It should also be appreciated that the methodsdescribed above may be performed by hardware components or may beembodied in sequences of machine- or processor-executable instructions,which may be used to cause a machine or one or more processors toperform the methods. These machine-executable instructions may be storedon one or more machine readable mediums, such as CD-ROMs or other typeof optical disks, floppy diskettes, ROMs, RAMs, EPROMs, EEPROMs,magnetic or optical cards, flash memory, or other types ofmachine-readable mediums suitable for storing electronic instructions.Alternatively, the methods may be performed by a combination of hardwareand software.

Where components are described as being configured to perform certainoperations, such configuration can be accomplished, for example, bydesigning electronic circuits or other hardware to perform theoperation, by programming programmable electronic circuits (e.g.,microprocessors, or other suitable electronic circuits) to perform theoperation, or any combination thereof.

While illustrative embodiments of the application have been described indetail herein, it is to be understood that the inventive concepts may beotherwise variously embodied and employed, and that the appended claimsare intended to be construed to include such variations, except aslimited by the prior art.

We claim:
 1. A system for generating communications based on variant information and sensor data, comprising: one or more hardware processors; and a non-transitory computer readable storage medium in data communication with the one or more hardware processors, the non-transitory computer readable storage medium comprising instructions that, when executed by the one or more hardware processors, cause the one or more hardware processors to perform operations including: obtaining, at the one or more hardware processors, genetic-variant data corresponding to one or more variants associated with a client, wherein each of the one or more variants corresponds to an instance of one or more bases positioned at one or more first positions in a first genetic sequence differing from a corresponding one or more bases positioned at corresponding one or more second positions in a reference genetic sequence, wherein the first genetic sequence is a genetic sequence of the client; obtaining sensor data providing an indication of a current circumstance of the client; processing the genetic-variant data and the sensor data to generate a disease-risk metric corresponding to a predicted risk of the client developing a particular disease; generating a communication indicative of the disease-risk metric; and transmitting the communication to a remote device.
 2. The system for generating communications based on variant information and sensor data as recited in claim 1, wherein the operations further include: performing a second disease-risk analysis using the genetic-variant data corresponding to one or more variants, wherein the second disease-risk analysis corresponds to determination of a second disease-risk metric for the client; generating a second communication indicative of the second disease-risk metric; and transmitting the second communication to the remote device.
 3. The system for generating communications based on variant information and sensor data as recited in claim 1, wherein the operations further include: identifying an aggregated disease-risk metric for a plurality of other clients different from the client, wherein the communication includes the aggregated disease-risk metric.
 4. The system for generating communications based on variant information and sensor data as recited in claim 1, wherein the operations further include: generating one or more targets for the client, wherein the one or more targets are associated with changing the disease-risk metric for the client, and wherein the communication includes the one or more targets.
 5. The system for generating communications based on variant information and sensor data as recited in claim 4, wherein the operations further include: receiving additional sensor data providing an updated indication of an updated quality of the client; performing a second disease-risk analysis using the genetic-variant data corresponding to one or more variants, the sensor data, and the additional sensor data, wherein the second disease-risk analysis corresponds to determination of a second disease-risk metric for the client; generating a second communication indicative of the second disease-risk metric; and transmitting the second communication.
 6. The system for generating communications based on variant information and sensor data as recited in claim 1, wherein the operations further include: transmitting a request for permission to access the genetic-variant data corresponding to one or more variants associated with the client; receiving a response including authorization to access the genetic-variant data corresponding to one or more variants associated with the client; and using the authorization in obtaining the genetic-variant data corresponding to one or more variants.
 7. The system for generating communications based on variant information and sensor data as recited in claim 1, wherein the sensor data includes one or more of chemical sensor data, potentiometric sensor data, solute sensor data, microfluidic sensor data, biometric sensor data, biomarker sensor data, pH sensor data, cytometric sensor data, optical sensor data, electrical current sensor data, electrical resistance sensor data, and electrical impedance sensor data.
 8. The system for generating communications based on variant information and sensor data as recited in claim 1, wherein the sensor data corresponds to sensor data obtained by one or more sensors associated with or worn by the client.
 9. The system for generating communications based on variant information and sensor data as recited in claim 1, wherein obtaining the sensor data includes: transmitting a query to a second remote device, wherein the query includes a request for the sensor data associated with the client; and receiving, in response to the query, the sensor data.
 10. The system of claim 1, wherein the operations further include: determining, at the one or more hardware processors, that the first genetic sequence includes the one or more variants; accessing a work flow for assigning variants to categories, wherein the work flow includes a plurality of stages organized according to a hierarchical structure, and wherein a trajectory through the work flow is determined based on successive results generated for one or more of the plurality of stages; for each variant of the one or more variants, performing a work flow iteration by: iteratively performing, at the one or more hardware processors, an automated processing in accordance with each of one or more stages of the plurality of stages according to the work flow based on at least one of: a position associated with the variant; the one or more bases associated with the variant; and a result of a previous stage; wherein a result of the stage is generated at least partly in response to the automated processing, and wherein a next stage is determined based on the result of the stage; wherein performing an automated processing in accordance with a stage of the one or more stages includes: performing, at the one or more hardware processors, a look-up function using an identifier of the variant to determine whether stored data indicates that the variant is to be assigned to a specific category of a plurality of categories; and generating the result of the iterative performance of the automated processing that identifies the specific category when the stored data indicates that the variant is to be assigned to the specific category; and assigning the variant to a category of the plurality of categories based on results of the iterative performance of the automated processing; determining whether a number of variants assigned to a particular category of the plurality of categories exceeds a predefined threshold; and generating a second communication indicative of whether a number of variants assigned to the particular category exceeds the predefined threshold.
 11. The system of claim 1, wherein the operations further include: receiving, using the one or more hardware processors, requests from a plurality of client devices for assessing genetic risks associated with a first medical condition, wherein the plurality of client devices are respectively associated with a plurality of clients; determining genetic information for each of the plurality of clients, wherein genetic information for a client includes sequence information for a plurality of genes for the client; analyzing a first subset of the genetic information to obtain respective genetic risk assessment results for each of the plurality of clients, wherein the respective genetic risk assessment results are associated with the first medical condition; making the respective genetic risk assessment results available to the plurality of clients; determining a plurality of permissions, each permission corresponding to an authorization provided by a particular client for sharing the sequence information for the plurality of genes for the particular client with one or more external assessment systems, wherein an external assessment system corresponds to a remote system distinct from the one or more hardware processors, and wherein the external assessment system has independent access to a data store including analysis results generated by the external assessment system; after determining the plurality of permissions, receiving a data request from a particular external assessment system, wherein the data request corresponds to a request for sequence information for one or more genes for each of the plurality of clients for assessing genetic risks associated with a second medical condition different from the first medical condition, wherein the sequence information for the one or more genes corresponds to a second subset of the genetic information, and wherein the second subset of the genetic information is at least partially different from the first subset of the genetic information; determining that an access authorization level for the particular external assessment system is sufficient for accessing the second subset of the genetic information; determining that the plurality of permissions authorize sharing the second subset of the genetic information for each of the plurality of clients with external assessment systems; obtaining the second subset of the genetic information for each of the plurality of clients and contact information for each of the plurality of clients; and transmitting a response to the data request, wherein the response to the data request includes the second subset of the genetic information for each of the plurality of clients and the contact information for each of the plurality of clients, and wherein receiving the second subset of the genetic information for each of the plurality of clients at the particular external assessment system facilitates the particular external assessment system generating second respective genetic risk assessment results associated with the second medical condition using the second subset of the genetic information, and receiving the contact information for each of the plurality of clients at the particular external assessment system facilitates the particular external assessment system providing the second respective genetic risk assessment results to the plurality of client devices.
 12. The system of claim 1, wherein the operations further include: for each client of a set of clients: receiving, using the one or more hardware processors, a set of reads, each read of the set of reads being associated with the client of the set of clients, each read of the set of reads including a set of identifiers, the set of identifiers being arranged in a particular order in the read; aligning each read of the set of reads with a portion of a reference data set; and generating a depth vector for the client of the set of clients that includes a plurality of elements, each element of the plurality of elements being generated based on a quantity of reads that include an identifier aligned to a portion that includes a particular position within the reference data set; and performing, using the one or more hardware processors, a transformation processing of the depth vectors to produce a plurality of components, each component of the plurality of components assigned a component order based on an extent to which the component accounts for cross-client differences; identifying a subset of the plurality of components based on the component order; and for each component in the subset: generating, for each client of the set of clients, a weight for the component; determining, for each client of the set of clients, that the weight for the component indicates that the client is to be associated with a new variant; determining positional data for the new variant based on values in the component; and storing, for each client of the set of clients, an association between an identifier of the client of the set of clients and variant data that includes the positional data.
 13. A computer implemented method for generating communications based on variant information and sensor data, the method comprising: obtaining, at one or more hardware processors, genetic-variant data corresponding to one or more variants associated with a client, wherein each of the one or more variants corresponds to an instance of one or more bases positioned at one or more first positions in a first genetic sequence differing from a corresponding one or more bases positioned at corresponding one or more second positions in a reference genetic sequence, wherein the first genetic sequence is a genetic sequence of the client; obtaining sensor data providing an indication of a current circumstance of the client; processing the genetic-variant data and the sensor data to generate a disease-risk metric corresponding to a predicted risk of the client developing a particular disease; generating a communication indicative of the disease-risk metric; and transmitting the communication to a remote device.
 14. The method for generating communications based on variant information and sensor data as recited in claim 13, further comprising: performing a second disease-risk analysis using the genetic-variant data corresponding to one or more variants, wherein the second disease-risk analysis corresponds to determination of a second disease-risk metric for the client; generating a second communication indicative of the second disease-risk metric; and transmitting the second communication to the remote device.
 15. The method for generating communications based on variant information and sensor data as recited in claim 13, further comprising: identifying an aggregated disease-risk metric for a plurality of other clients different from the client, wherein the communication includes the aggregated disease-risk metric.
 16. The method for generating communications based on variant information and sensor data as recited in claim 13, further comprising: generating one or more targets for the client, wherein the one or more targets are associated with changing the disease-risk metric for the client, and wherein the communication includes the one or more targets.
 17. The method for generating communications based on variant information and sensor data as recited in claim 16, further comprising: receiving additional sensor data providing an updated indication of an updated quality of the client; performing a second disease-risk analysis using the genetic-variant data corresponding to one or more variants, the sensor data, and the additional sensor data, wherein the second disease-risk analysis corresponds to determination of a second disease-risk metric for the client; generating a second communication indicative of the second disease-risk metric; and transmitting the second communication.
 18. The method for generating communications based on variant information and sensor data as recited in claim 13, further comprising: transmitting a request for permission to access the genetic-variant data corresponding to one or more variants associated with the client; receiving a response including authorization to access the genetic-variant data corresponding to one or more variants associated with the client; and using the authorization in obtaining the genetic-variant data corresponding to one or more variants.
 19. The method for generating communications based on variant information and sensor data as recited in claim 13, wherein the sensor data includes one or more of chemical sensor data, potentiometric sensor data, solute sensor data, microfluidic sensor data, biometric sensor data, biomarker sensor data, pH sensor data, cytometric sensor data, optical sensor data, electrical current sensor data, electrical resistance sensor data, and electrical impedance sensor data.
 20. A non-transitory computer readable storage medium for generating communications based on variant information and sensor data, the non-transitory computer readable storage medium comprising instructions that, when executed by one or more hardware processors, cause the one or more hardware processors to perform operations including: obtaining, at one or more hardware processors, genetic-variant data corresponding to one or more variants associated with a client, wherein each of the one or more variants corresponds to an instance of one or more bases positioned at one or more first positions in a first genetic sequence differing from a corresponding one or more bases positioned at corresponding one or more second positions in a reference genetic sequence, wherein the first genetic sequence is a genetic sequence of the client; obtaining sensor data providing an indication of a current circumstance of the client; processing the genetic-variant data and the sensor data to generate a disease-risk metric corresponding to a predicted risk of the client developing a particular disease; generating a communication indicative of the disease-risk metric; and transmitting the communication to a remote device. 